Multiple notification user interface

ABSTRACT

The present disclosure generally relates to audio output for time-based notifications. Enhanced alerts for time-based notifications based on various notification conditions provides users with clarity about which notifications are being output, thereby providing an improved user interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. non-Provisional applicationSer. No. 17/750,095, entitled “MULTIPLE NOTIFICATION USER INTERFACE”,filed May 20, 2022, which is a continuation of U.S. non-Provisionalapplication Ser. No. 16/147,406, entitled “MULTIPLE NOTIFICATION USERINTERFACE”, filed Sep. 28, 2018, now U.S. Pat. No. 11,340,962, whichclaims priority to U.S. Provisional Application No. 62/729,939, entitled“MULTIPLE NOTIFICATION USER INTERFACE”, filed Sep. 11, 2018, the entirecontents of each are hereby incorporated by reference.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for time-based notification audiooutput.

BACKGROUND

The number of electronic devices, and particularly smart devices, inusers' homes continues to increase. These devices are increasingly beinginterconnected with each other, are increasingly more capable, and areperforming more complex tasks. As such, these devices are increasinglyexpected to have thoughtfully-designed user interfaces.

BRIEF SUMMARY

Some techniques for time-based notification audio output usingelectronic devices, however, are not informative and are generallycumbersome and inefficient. For example, some existing techniques use acomplex and time-consuming user interface, which may include multiplekey presses or keystrokes. For another example, some existing techniquesdo not sufficiently indicate and or identify multiple expired time-basednotifications. Some existing techniques are confusing, and require moretime than necessary, wasting user time and device energy. This latterconsideration is particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for time-basednotification audio output. Such methods and interfaces optionallycomplement or replace other methods for time-based notification audiooutput. Such methods and interfaces reduce the cognitive burden on auser and produce a more efficient human-machine interface. Forbattery-operated computing devices, such methods and interfaces conservepower and increase the time between battery charges. Such methods andinterfaces also reduce the number of repetitive, unnecessary, and/orextraneous inputs required by a user and produce a more efficienthuman-machine interface.

In accordance with some embodiments, a method is performed at anelectronic device. The method comprises: receiving informationrepresenting a first time-based notification condition; setting a firsttime-based notification based on the first time-based notificationcondition; and in response to a determination that the first time-basednotification condition has occurred: in accordance with a determinationthat the electronic device is not currently causing output of an audionotification based on at least one time-based notification other thanthe first time-based notification, causing output of a first audionotification; and in accordance with a determination that the electronicdevice is currently causing output of the audio notification based on atleast one time-based notification other than the first time-basednotification, causing output of a second audio notification differentfrom the first audio notification.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device, the one or more programsincluding instructions for: receiving information representing a firsttime-based notification condition; setting a first time-basednotification based on the first time-based notification condition; andin response to a determination that the first time-based notificationcondition has occurred: in accordance with a determination that theelectronic device is not currently causing output of an audionotification based on at least one time-based notification other thanthe first time-based notification, causing output of a first audionotification; and in accordance with a determination that the electronicdevice is currently causing output of the audio notification based on atleast one time-based notification other than the first time-basednotification, causing output of a second audio notification differentfrom the first audio notification.

In accordance with some embodiments, an electronic device is described.The electronic device comprises: one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:receiving information representing a first time-based notificationcondition; setting a first time-based notification based on the firsttime-based notification condition; and in response to a determinationthat the first time-based notification condition has occurred: inaccordance with a determination that the electronic device is notcurrently causing output of an audio notification based on at least onetime-based notification other than the first time-based notification,causing output of a first audio notification; and in accordance with adetermination that the electronic device is currently causing output ofthe audio notification based on at least one time-based notificationother than the first time-based notification, causing output of a secondaudio notification different from the first audio notification.

In accordance with some embodiments, an electronic device is described.The electronic device comprises: means for receiving informationrepresenting a first time-based notification condition; means forsetting a first time-based notification based on the first time-basednotification condition; and responsive to a determination that the firsttime-based notification condition has occurred: in accordance with adetermination that the electronic device is not currently causing outputof an audio notification based on at least one time-based notificationother than the first time-based notification, means for causing outputof a first audio notification; and in accordance with a determinationthat the electronic device is currently causing output of the audionotification based on at least one time-based notification other thanthe first time-based notification, means for causing output of a secondaudio notification different from the first audio notification.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for: receiving information representinga first time-based notification condition; setting a first time-basednotification based on the first time-based notification condition; andin response to a determination that the first time-based notificationcondition has occurred: in accordance with a determination that theelectronic device is not currently causing output of an audionotification based on at least one time-based notification other thanthe first time-based notification, causing output of a first audionotification; and in accordance with a determination that the electronicdevice is currently causing output of the audio notification based on atleast one time-based notification other than the first time-basednotification, causing output of a second audio notification differentfrom the first audio notification.

In accordance with some embodiments, a method is performed at anelectronic device. The method comprises: receiving informationrepresenting a first time-based notification condition; setting a firsttime-based notification based on the first time-based notificationcondition; and in response to a determination that the first time-basednotification condition has occurred: causing output of an audionotification; in accordance with a determination that a set of one ormore name output conditions is satisfied, causing output of an audioidentifier that identifies the first time-based notification; and inaccordance with a determination that the set of one or more name outputconditions is not satisfied, forgoing causing output of the audioidentifier that identifies the first time-based notification, whereinthe set of one or more name output conditions includes a first conditionthat is satisfied when a second time-based notification is active whenthe first time-based notification condition occurs, and wherein the setof one or more name output conditions is satisfied when at least onename output condition in the set of one or more name output conditionsis satisfied.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device, the one or more programsincluding instructions for: receiving information representing a firsttime-based notification condition; setting a first time-basednotification based on the first time-based notification condition; andin response to a determination that the first time-based notificationcondition has occurred: causing output of an audio notification; inaccordance with a determination that a set of one or more name outputconditions is satisfied, causing output of an audio identifier thatidentifies the first time-based notification; and in accordance with adetermination that the set of one or more name output conditions is notsatisfied, forgoing causing output of the audio identifier thatidentifies the first time-based notification, wherein the set of one ormore name output conditions includes a first condition that is satisfiedwhen a second time-based notification is active when the firsttime-based notification condition occurs, and wherein the set of one ormore name output conditions is satisfied when at least one name outputcondition in the set of one or more name output conditions is satisfied.

In accordance with some embodiments, an electronic device is described.The electronic device comprises: one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:receiving information representing a first time-based notificationcondition; setting a first time-based notification based on the firsttime-based notification condition; and in response to a determinationthat the first time-based notification condition has occurred: causingoutput of an audio notification; in accordance with a determination thata set of one or more name output conditions is satisfied, causing outputof an audio identifier that identifies the first time-basednotification; and in accordance with a determination that the set of oneor more name output conditions is not satisfied, forgoing causing outputof the audio identifier that identifies the first time-basednotification, wherein the set of one or more name output conditionsincludes a first condition that is satisfied when a second time-basednotification is active when the first time-based notification conditionoccurs, and wherein the set of one or more name output conditions issatisfied when at least one name output condition in the set of one ormore name output conditions is satisfied.

In accordance with some embodiments, an electronic device is described.The electronic device comprises: means for receiving informationrepresenting a first time-based notification condition; means forsetting a first time-based notification based on the first time-basednotification condition; and responsive to a determination that the firsttime-based notification condition has occurred: means for causing outputof an audio notification; in accordance with a determination that a setof one or more name output conditions is satisfied, means for causingoutput of an audio identifier that identifies the first time-basednotification; and in accordance with a determination that the set of oneor more name output conditions is not satisfied, means for forgoingcausing output of the audio identifier that identifies the firsttime-based notification, wherein the set of one or more name outputconditions includes a first condition that is satisfied when a secondtime-based notification is active when the first time-based notificationcondition occurs, and wherein the set of one or more name outputconditions is satisfied when at least one name output condition in theset of one or more name output conditions is satisfied.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display, the one or moreprograms including instructions for: receiving information representinga first time-based notification condition; setting a first time-basednotification based on the first time-based notification condition; andin response to a determination that the first time-based notificationcondition has occurred: causing output of an audio notification; inaccordance with a determination that a set of one or more name outputconditions is satisfied, causing output of an audio identifier thatidentifies the first time-based notification; and in accordance with adetermination that the set of one or more name output conditions is notsatisfied, forgoing causing output of the audio identifier thatidentifies the first time-based notification, wherein the set of one ormore name output conditions includes a first condition that is satisfiedwhen a second time-based notification is active when the firsttime-based notification condition occurs, and wherein the set of one ormore name output conditions is satisfied when at least one name outputcondition in the set of one or more name output conditions is satisfied.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for time-based notification audio output, thereby increasingthe effectiveness, efficiency, and user satisfaction with such devices.Such methods and interfaces may complement or replace other methods fortime-based notification audio output.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 5C illustrates an electronic device in accordance with someembodiments.

FIG. 5D is a block diagram illustrating an electronic device inaccordance with some embodiments.

FIGS. 6A-6O illustrate exemplary techniques and user interfaces foroutputting multiple-event audio notifications.

FIGS. 7A-7B is a flow diagram illustrating a process for outputtingmultiple-event audio notifications.

FIGS. 8A-8O illustrate exemplary techniques and user interfaces foroutputting audio identifiers for time-based notifications.

FIGS. 9A-9B is a flow diagram illustrating a process for outputtingaudio identifiers for time-based notifications.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for audio output of time-based notifications. Forexample, techniques that sufficiently indicate and/or identify multipleexpired time-based notifications. Such techniques can reduce thecognitive burden on a user who interacts with time-based notifications,thereby enhancing productivity. Further, such techniques can reduceprocessor and battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5D provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-6O illustrate exemplary user interfaces formanaging event notifications. FIGS. 7A-7B is a flow diagram illustratingmethods of managing event notifications in accordance with someembodiments. The user interfaces in FIGS. 6A-6G are used to illustratethe processes described below, including the processes in FIGS. 7A-7B.FIGS. 8A-8O illustrate exemplary user interfaces for accessing eventnotifications. FIGS. 9A-9B is a flow diagram illustrating methods ofaccessing event notifications in accordance with some embodiments. Theuser interfaces in FIGS. 8A-8O are used to illustrate the processesdescribed below, including the processes in FIGS. 9A-9B.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “it” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPadsdevices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch screen displays and/or touchpads),are, optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for c-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. U/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2 ) optionally include an up/downbutton for volume control of speaker 111 and/or microphone 113. The oneor more buttons optionally include a push button (e.g., 206, FIG. 2 ).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts module 137, e-mail client module 140, IMmodule 141, browser module 147, and any other application that needstext input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone module138 for use in location-based dialing; to camera module 143 aspicture/video metadata; and to applications that provide location-basedservices such as weather widgets, local yellow page widgets, andmap/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone module 138, video conference module 139, e-mail client module140, or IM module 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo!Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an c-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UT) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US20131040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013.1069483, titled “Device, Method, and GraphicalUser Interface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700 and900 (FIGS. 7 and 9 ). A computer-readable storage medium can be anymedium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0, 1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location), In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

FIG. 5C illustrates exemplary electronic device 580. Device 580 includesbody 580A. In some embodiments, device 580 can include some or all ofthe features described with respect to devices 100, 300, and 500 (e.g.,FIGS. 1A-5B). In some embodiments, device 580 has one or more speakers580B (concealed in body 580A), one or more microphones 580C, one or moretouch-sensitive surfaces 580D, and one or more displays 580E.Alternatively, or in addition to a display and touch-sensitive surface580D, the device has a touch-sensitive display (also referred to as atouchscreen). As with devices 100, 300, and 500, in some embodiments,touch-sensitive surface 580D (or the touch screen) optionally includesone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors oftouch-sensitive surface 580D (or the touchscreen) can provide outputdata that represents the intensity of touches. The user interface ofdevice 580 can respond to touches based on their intensity, meaning thattouches of different intensities can invoke different user interfaceoperations on device 580. In some embodiments, the one or more displays580E are one or more light-emitting diodes (LEDs). For example, adisplay can be a single LED, an LED cluster (e.g., a red, a green, and ablue LED), a plurality of discrete LEDs, a plurality of discrete LEDclusters, or other arrangement of one or more LEDs. For example, thedisplay 580E can be an array of nine discrete LED clusters arranged in acircular shape (e.g., a ring). In some examples, the one or moredisplays are comprised of one or more of another type of light-emittingelements.

FIG. 5D depicts exemplary personal electronic device 580. In someembodiments, device 580 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, 3 , and 5A-5B. Device 580 hasbus 592 that operatively couples I/O section 594 with one or morecomputer processors 596 and memory 598. I/O section 594 can be connectedto display 582, which can have touch-sensitive component 584 and,optionally, intensity sensor 585 (e.g., contact intensity sensor). Insome embodiments, touch-sensitive component 584 is a separate componentthan display 582. In addition, I/O section 594 can be connected withcommunication unit 590 for receiving application and operating systemdata, using Wi-Fi, Bluetooth, near field communication (NFC), cellular,and/or other wireless communication techniques. Device 580 can includeinput mechanisms 588. Input mechanism 588 is, optionally, a button, insome examples. Input mechanism 588 is, optionally, a microphone, in someexamples. Input mechanism 588 is, optionally, a plurality of microphones(e.g., a microphone array).

Electronic device 580 includes one or more speakers 586 for outputtingaudio. Device 580 can include audio circuitry (e.g., in I/O section 594)that receives audio data, converts the audio data to an electricalsignal, and transmits the electrical signal to speaker 586. Speaker 586converts the electrical signal to human-audible sound waves. The audiocircuitry (e.g., in I/O section 594) also receives electrical signalsconverted by a microphone (e.g., input mechanism 588) from sound waves.The audio circuitry (e.g., in I/O section 594) converts the electricalsignal to audio data. Audio data is, optionally, retrieved from and/ortransmitted to memory 598 and/or RF circuitry (e.g., in communicationunit 590) by I/O section 594.

Memory 598 of personal electronic device 580 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 596, for example, can cause the computer processorsto perform the techniques described below, including processes 700 and900 (FIGS. 7 and 9 ). A computer-readable storage medium can be anymedium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device580 is not limited to the components and configuration of FIG. 5D, butcan include other or additional components in multiple configurations.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6O illustrate exemplary user interfaces and techniques foroutputting multiple-event audio notifications, in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIGS. 7A-7B.

FIGS. 6A-6B illustrate an exemplary technique for causing an electronicdevice to set a time-based notification. In some embodiments, device 600includes one or more features of devices 100, 300, 500, or 580. In FIGS.6A-6N, a device status box 601 indicates a status of the state ofelectronic device 600 and is provided as a visual indication of a statusof any time-based indicators that are set (e.g., in memory of device600) in the respective example scenario depicted in each respectivefigure. Device status box 601 is provided merely as a visual aid forease of the reader's understanding, and is not necessarily displayed bya device (e.g., 600). Additionally, unless otherwise noted in a figureor herein, device status box 601 indicates the status of device 600after any voice input (which can also referred to as a “command”, “voiceinput command”, or “voice command”) and any audio output depicted in therespective figure.

Turning to FIG. 6A, as noted in device status box 601, no time-basednotifications are set (e.g., in memory of device 600) before voice input604. That is, in FIG. 6A, status box 601 identifies that no time-basednotifications are set (“NONE”) before the device 600 receives voiceinput command 604.

In some embodiments, an electronic device (e.g., 600) receivesinformation (e.g., 604) representing a time-based notificationcondition. In some embodiments, the information is received as a voiceinput (e.g., 604). For example, as illustrated in FIG. 6A, device 600detects (e.g., via one or more microphones) exemplary voice input 604provided by user 602 that includes information representing a time-basednotification condition. In this example, the time-based notificationcondition is ten minutes elapsing (e.g., a timer of length ten minutes).

In some embodiments, the information representing the time-basednotification condition is part of a request to create a time-basednotification. For example, voice input 604 includes the phrase: “HEYSIRI, SET A TIMER FOR TEN MINUTES”. Thus, voice input 604 includes thefollowing information: a timer should be set (an exemplary request toset a timer type of time-based notification), the timer having a lengthof ten minutes (an exemplary time-based notification condition).

In some embodiments, voice input (e.g., that includes information abouta time-based notification condition) includes information other than(e.g., in addition to) a time-based notification condition. In someembodiments, a voice input includes a trigger phrase. For example, asshown in FIG. 6A, voice input 604 includes the exemplary trigger phrase“HEY SIRI”. In some embodiments, an electronic device (e.g., 600)listens for the trigger phrase and, once the trigger phrase is detected,begins transcribing and parsing the voice input that follows the triggerphrase. The trigger phrase “HEY SIRI” is used here merely as an example,and any other trigger phrase (or none) can be used when detecting voiceinput. In some embodiments, the electronic device listens for voiceinput in response to a non-voice input (e.g., a touch input). Forexample, a touch gesture on an affordances or a touch-sensitive surface(e.g., 580D) of electronic device 600 can cause the device to beginlistening for voice input (e.g., and transcribing and parsing such voiceinput). In some embodiments, the electronic device transcribes andparses voice input to determine information. For example, as shown inFIG. 6A, the device 600 transcribes and parses the phrase “HEY SIRI, SETA TIMER FOR TEN MINUTES” to determine that the trigger phrase wasdetected (“HEY SIR n”), that a timer should be set (“SET A TIMER”), andthat a notification condition for the timer will be occurrence oftenminutes elapsing (“FOR TEN MINUTES”).

FIG. 6B illustrates an exemplary response to receiving informationrepresenting a time-based notification condition. In some embodiments,the electronic device (e.g., 600) sets a first time-based notificationbased on the received information representing the time-basednotification condition. For example, in response to detecting voiceinput 604, electronic device 600 sets a timer having a notificationcondition that occurs when ten minutes have passed. As shown in FIG. 63, in response to voice input 604, electronic device 600 has set TIMER 1named “TEN MINUTE”, as indicated by device status box 601 in FIG. 6B.Device status box 601 in FIG. 6B also indicates the time remaining onthe timer named “TEN MINUTE”, which is 9:59 (nine minutes and fifty-nineseconds). In this example, one second has elapsed since creation of the“TEN MINUTE” timer, which had an original duration of ten minutes. Insome embodiments, setting a time-based notification includes invoking asoftware routine, software subroutine, software program, softwareapplication, and/or hardware to begin monitoring for occurrence of thetime-based notification condition of the time-based notification. Forexample, electronic device 600 begins a timer (for ten minutes) thatcreates an event or flag in software upon occurrence of ten minutespassing.

In some embodiments, the electronic device (e.g., 600) causes output ofan acknowledgement (e.g., audio output 606) of voice input (e.g., 604).In some embodiments, the electronic device outputs the acknowledgementin response to a command (e.g., “SET A TIMER”) detected in receivedvoice input. For example, as shown in FIG. 6B, in response to detectingvoice input 604 (FIG. 6A), device 600 outputs audio output 606, which isan acknowledgement of voice input 604 and indicates that the electronicdevice 600 set a ten minute timer.

In some embodiments, information representing a time-based notificationcondition and/or a request to set a time-based notification are receivedfrom a second device that is connected to the electronic device (e.g.,600). For example, a user can use a companion device (e.g., a device,other than device 600, that includes one or more features of devices100, 300, 500, or 580) to send data to the electronic device 600 (e.g.,the data including the information regarding the time-based notificationcondition and that causes the notification to be set). For example, thecompanion device can communicate with electronic device 600 via a Wi-Ficonnection, a Bluetooth connection, or other suitable communicationlink.

FIGS. 6C-6D illustrate an exemplary technique for outputting an audionotification for a single time-based notification. FIG. 6C depicts theelectronic device 600 just before TIMER 1 named “TEN MINUTE” (e.g., setas shown in FIGS. 6A-6B) expires. As shown in status box 601, the timer(TIMER 1) named “TEN MINUTE” has 0:01 remaining (zero minutes and onesecond), and there is no other time-based notification (e.g., timer,alarm) currently set.

FIG. 6D depicts the electronic device 600 just after TIMER 1 named “TENMINUTE” (e.g., set as shown in FIGS. 6A-6B) expires. In someembodiments, in response to a determination that a time-basednotification condition has occurred, the electronic device (e.g., 600)causes output of an audio notification. As shown in status box 601, thetimer (TIMER 1) named “TEN MINUTE” has 0:00 remaining (no timeremaining), and there is no other time-based notification (e.g., timer,alarm) currently set and that has expired but has not been dismissed. Insome embodiments, in accordance with a determination that the electronicdevice is not currently causing output of an audio notification (e.g.,for any time-based notification) when the time-based notificationcondition occurs, the electronic device causes output of a first audionotification. For example, when a timer's determined length of timeexpires (e.g., ten minutes have elapsed from the TEN MINUTE timer), thetime-based notification's notification condition occurs (which can alsobe referred to as the timer “going off”). As a result, the electronicdevice outputs (e.g., via an audio output device of the device) and/orcauses output of (e.g., by an external audio output device, such as aspeaker (e.g., 586), via a connection (e.g., via communication unit590)) an audio notification. The audio notification acts as an alert(e.g., to a user) that the notification condition has occurred. As shownin FIG. 6D, device 600 is outputting audio output 608, which includesoutput of an exemplary audio notification referred to as “AUDIONOTIFICATION 1”.

In this example, audio output 608 is provided as an illustration of theaudio notification that is output in the scenario depicted, and is notintended to preclude the output of an audio identifier (e.g., a name)for a time-based notification in the given exemplary scenario. Forexample, audio output 608 can represent a simplified representation ofaudio output 622 (FIG. 6K) or audio output 624 (FIG. 6L). Techniques fordetermining whether to output an audio identifier are discussed ingreater detail below.

In some embodiments, an audio notification is a media entity played backby an electronic device (e.g., 600). For example, an audio notificationcan be a media entity (e.g., a sound file) that lasts for some length oftime (e.g., a beginning time and an end time). The media entity can beplayed back once, or repeated one or more times (e.g., if it has a shortlength of time). A media entity, for example, can include one or moreaudio tones (e.g., an ascending scale of notes, a descending scale ofnotes, a song, or the like).

In some embodiments, a first audio notification is a single-event audionotification. For example, electronic device 600 plays a single-eventaudio notification when there is only one time-based notificationcondition that has occurred that has not been dismissed (e.g., by useraction, or by timing out after some amount of time, or other dismissalevent). For example, “AUDIO NOTIFICATION 1” is an exemplary single-eventaudio notification.

In some embodiments, the electronic device is capable of setting a firsttype of time-based notification and a second type of time-basednotification. For example, a first type can be a timer type ofnotification and a second type can be an alarm type of notification. Inanother example, the first type is alarm and the second type is timers.In some embodiments, a single-event audio notification is a single-eventaudio notification for a first type of time-based notification. When asingle time-based notification has expired and is a first type oftime-based notification, the audio notification output is a single-eventaudio notification for the first type. In some embodiments, asingle-event audio notification is a single-event audio notification fora second type of time-based notification. When a single time-basednotification has expired and is a second type of time-basednotification, the audio notification output is a single-event audionotification for the second type. In some embodiments, the single-eventaudio notification for the first type and the single-event audionotification for the second type are different. For example, they can bedifferent media entities that sound different when played back, thusproviding an indication of the type of time-based notification goingoff.

FIGS. 6E-6H illustrate an exemplary technique for outputting an audionotification for multiple time-based notifications. In some embodiments,the electronic device sets a first time-based notification and a secondtime-based notification. For example, as shown in status box 601 in FIG.6E, an exemplary first time-based notification is already set: TIMER 1(named “TEN MINUTE”), created as shown in FIGS. 6A-6B, that has 7:59(seven minutes and fifty-nine seconds) remaining before the command invoice input 610 is received (as indicated in status box 601).Additionally, in FIG. 6E, electronic device detects voice input 610(uttered by user 602), representing a request to create a secondtime-based notification (e.g., a timer) that includes a secondtime-based notification condition (e.g., five-minute length of time).

Turning to FIG. 6F, in response to receiving voice input 610, electronicdevice sets a second time-based notification based on the secondtime-based notification condition. As shown in FIG. 6F, status box 601now indicates that an exemplary second-time based notification TIMER 2(named “FIVE MINUTE”) is set on electronic device 600, and has 4:59(four minutes and fifty-nine seconds) remaining. Additionally, in FIG.6F, four seconds have elapsed from TIMER 1 since before voice input 610was detected in FIG. 6E—in FIG. 6F, TIMER 1 is now has 7:55 (sevenminutes and fifty-five seconds) remaining. In some embodiments, theelectronic device (e.g., 600) causes output of an audio acknowledgementof audio input. For example, in FIG. 6F, electronic device 600 outputs(e.g., text-to-speech dictation output) acknowledgement 612 which states“FIFTEEN MINUTE TIMER, STARTING NOW” and acknowledges that a secondtimer (TIMER 2) has been set and is starting.

It should be appreciated that the exact moment that the timer begins isnot necessarily tied to the timing of the text-to-speech output (e.g.,acknowledgement 612) of an electronic device (e.g., 600). For example,an acknowledgement (e.g., 612) can be provided as merely a generalindication to a user (e.g., 602) that a timer has just been started.Thus, for instance, TIMER 2 can be started after voice input 610 butbefore acknowledgement 612 is output, during output of acknowledgement612, or after output of acknowledgement 612.

Notably, as described herein, the time remaining on a timer representsthe time remaining until expiration of a timer (e.g., a length of timethat counts down). However, a timer can also be represented (e.g.,implemented in a program) as an amount of time that counts up to a goalvalue. Either are intended to be within the scope of this disclosurewith respect to the term “timer”.

In some embodiments, the electronic device (e.g., 600) receives arequest for a status of a time-based notification. For example, device600 receives voice input “HEY SIRI, HOW MUCH TIME IS LEFT ON MY TENMINUTE TIMER?” in the scenario depicted in FIG. 6F. As shown in FIG. 6F,the TEN MINUTE timer has 7:55 (seven minutes and fifty-five seconds)remaining. In some embodiments, in response to receiving a request for astatus of a time-based notification, the electronic device (e.g., 600)provides a status of the corresponding time-based notification. In someembodiments, the status includes an amount of time remaining until thecorresponding time-based notification condition occurs. For example, inresponse to the voice input, device 600 outputs “THERE ARE SEVEN MINUTESAND FIFTY-FIVE SECONDS REMAINING ON YOUR TEN MINUTE TIMER”. In someembodiments, the status includes information about the correspondingtime-based notification condition. For example, device 600 receivesvoice input “WHAT TIME IS MY WAKE UP ALARM SET FOR?” and responds withthe output “YOUR WAKE UP ALARM IS SET FOR SEVEN FIFTEEN A.M.”.

In some embodiments, the electronic device (e.g., 600) receives arequest to change a time-based notification condition for an activetime-based notification. For example, with reference to the scenariodepicted in FIG. 6F, device 600 can receive voice input “HEY SIRI,CHANGE MY TEN MINUTE TIMER TO A TWENTY MINUTE TIMER”. As shown in FIG.6F, the TEN MINUTE timer has 7:55 (seven minutes and fifty-five seconds)remaining. In some embodiments, in response to receiving a request for astatus of a time-based notification, the electronic device (e.g., 600)changes the corresponding time-based notification condition based on therequest. For example, the TEN MINUTE timer can be extended to have 17:55(seventeen minutes and fifty-five seconds) remaining (e.g., thedifference between original length and the new length added to thecurrently running timer). A timer can be shortened, such as by “HEYSIRI, CHANGE MY TEN MINUTE TIMER TO A FOUR MINUTE TIMER”-thus, the TENMINUTE timer can be shorted to have 1:55 (one minute and fifty-fiveseconds) remaining (e.g., the difference between original length and thenew length removed from the currently running timer). In someembodiments, in response to receiving a request for a status of atime-based notification, the electronic device (e.g., 600) changes thename of the time-based notification based on the change to thecorresponding time-based notification condition. For example, a tenminute timer being extended to twenty minutes as described above causesrenaming from TEN MINUTE to TWENTY MINUTE, or being shortened asdescribed above causes renaming from TEN MINUTE to FOUR MINUTE. In someembodiments, the time-based notification is only renamed if the name ofthe time-based notification was not set by user input. For example ifthe timer being extended or shortened was named DINNER by the user, thenthe name DINNER would not be changed based on the change to thecorresponding time-based notification condition.

FIGS. 6G-6H illustrate an exemplary technique for outputting an audionotification for multiple time-based notifications. FIG. 6G depicts theelectronic device 600 just before TIMER 1 named “TEN MINUTE” (e.g., setas shown in FIGS. 6A-6B) expires. As shown in status box 601 of FIG. 6G,the timer (TIMER 1) named “TEN MINUTE” has 0:01 (zero minutes and onesecond) remaining. Thus, FIG. 6G illustrates a similar scenario as thatshown in FIG. 6C. However, in FIG. 6G, status box 601 also indicatesthat electronic device 600 has a second-time based notificationcurrently set, TIMER 2 (named “FIVE MINUTE”) with 0:00 (no time)remaining. Accordingly, because the second time-based notificationcondition has occurred (five minutes elapsed) for the second time-basednotification (“FIVE MINUTE” timer), and because only a singlenotification is currently causing audio output (e.g., only the FIVEMINUTE timer is going off), electronic device outputs the exemplarysingle-event audio notification “AUDIO NOTIFICATION 1” as discussedabove.

In this example, audio output 614 is provided as an illustration of theaudio notification that is output in the scenario depicted, and is notintended to preclude the output of an audio identifier (e.g., a name)for a time-based notification in the given exemplary scenario. Forexample, audio output 608 can represent a simplified representation ofaudio output 622 (FIG. 6K) or audio output 624 (FIG. 6L). Techniques fordetermining whether to output an audio identifier are discussed ingreater detail below.

Turning to FIG. 6H, an exemplary technique for causing output of amultiple-event notification is illustrated. For example, FIG. 6Hillustrates an exemplary scenario in which multiple time-basednotifications have expired and have not been dismissed. In someembodiments, in accordance with a determination that the electronicdevice (e.g., 600) is currently causing output of the audio notificationbased on at least one (e.g., TIMER 2) other time-based notification(e.g., other than TIMER 1), the electronic device causes output of asecond audio notification (e.g., AUDIO NOTIFICATION 2 in audio output616) different from the first audio notification (e.g., AUDIONOTIFICATION 1 in audio output 614 of FIG. 6G). For example, theelectronic device 600 determines that AUDIO NOTIFICATION 1 is currentlybeing output when the notification condition for TIMER 1 occurs, andthus causes output of AUDIO NOTIFICATION 2 as shown in audio output 616of FIG. 6H.

In this example, audio output 616 is provided as an illustration of theaudio notification that is output in the scenario depicted, and is notintended to preclude the output of an audio identifier (e.g., a name)for a time-based notification in the given exemplary scenario. Forexample, audio output 608 can represent a simplified representation ofaudio output 622 (FIG. 6K) or audio output 624 (FIG. 6L). Techniques fordetermining whether to output an audio identifier are discussed ingreater detail below.

In some embodiments, the second audio notification (e.g., AUDIONOTIFICATION 2) is a multiple-event audio notification. For example,status box 601 in FIG. 6H indicates that both TIMER 1 and TIMER 2 haveexpired and have not been dismissed. In the example in FIG. 611 ,electronic device 600 outputs exemplary multiple-event audionotification named AUDIO NOTIFICATION 2 when both the TEN MINUTE timerand the FIVE MINUTE timer are going off concurrently.

In the situation where two or more time-based notifications haveexpired, it can be useful to provide a multiple-event audio notificationthat is distinguishable from a single-event audio notification. Byproviding a multiple-event audio notification that is distinguishablefrom a single-event audio notification, a listener (e.g., user 602) caneasily determine that multiple time-based notifications are concurrentlygoing off (e.g., their notification conditions have occurred and thenotifications have not been dismissed). Thus, for example, when a singletimer expires and is causing an audio notification to be output, andthen a second timer expires, the user can easily determine that thesecond timer has expired based on a change in the audio notificationthat the electronic device outputs (e.g., a change in audio output froma single-event audio notification to a multiple-event audionotification). For example, a user can set multiple timers, each servingas a reminder to the user that they need to perform a respective task(e.g., remove a first item of food from the oven for a first timer, andcheck on a second item of food for a second timer)—thus, providing anindication that distinguishes when multiple timers are concurrentlygoing off provides the user with additional and useful information aboutthe state of the device.

In some embodiments, a multiple-event audio notification that is outputdepends on the number of time-based notifications that are concurrentlygoing off. For example, there can be an audio notification for twotime-based notifications, another audio notification for threetime-based notifications, and so on.

In some embodiments, the electronic device (e.g., 600) ceases output ofa first audio notification in accordance with a determination thatcauses output of a second audio notification. For example, in FIG. 6H,device 600 has ceased to output AUDIO NOTIFICATION 1 (as was output inFIG. 6G) and has begun to output AUDIO NOTIFICATION 2.

In some embodiments, the second audio notification cuts off the firstaudio notification. For example, an audio notification can be a mediaentity (e.g., a sound file) that lasts for some length of time (e.g., aplayback time, such as three seconds) as described above. If the secondaudio notification cuts off the first audio notification, the firstaudio notification stops playing abruptly (e.g., in the middle of thelength of time, immediately in response to a multiple-event conditionoccurring) and the second audio notification begins playing (e.g., uponthe first audio notification ceasing to be output). Thus, in FIG. 6H,AUDIO NOTIFICATION 1 stops being output in response to TIMER 1 expiringand AUDIO NOTIFICATION 2 begins being output.

As used herein, a “multiple-event condition” occurring includes asituation in which a second time-based notification condition hasoccurred while a first time-based notification is going off and has notbeen dismissed. A multiple-event condition occurring includes asituation in which two or more time-based notification conditions haveoccurred and have not been dismissed. As used herein, a “single-eventcondition” occurring includes a situation in which a first time-basednotification condition has occurred while no other time-basednotification is going off.

In some embodiments, the first audio notification is output until theend of its length of time (e.g., the full three seconds of playback)before device begins causing output of the second audio notification.For example, in FIG. 6G, AUDIO NOTIFICATION 1 can be allowed to finishplayback (e.g., until its end time) before device 600 begins outputtingAUDIO NOTIFICATION 2 as shown in FIG. 6H. In some examples, had thesecond time-based notification condition not occurred, the devicerepeatedly plays back (loops) the first audio notification untildismissed.

In some embodiments, a multiple-event audio notification adds onto anexisting single-event audio notification. For example, AUDIONOTIFICATION 2 can be a second media entity that includes the audiotones of AUDIO NOTIFICATION 1 (a first media entity), but includeadditional tones (e.g., when playback of AUDIO NOTIFICATION 1 normallyends), thus sounding like AUDIO NOTIFICATION 1 has been extended oraugmented. In this way, a transition from a single-event audionotification to a multiple-event audio notification is easily perceiveddue to the apparent change to the single-event audio notification (e.g.,change to a familiar sound that is already playing can be perceived bythe user).

In some embodiments, the first audio notification and the second audionotification are different, and the electronic device outputs bothduring a multiple-event condition. For example, the first audionotification is output during a single-event condition (e.g., TIMER 2expiring in FIG. 6G) and upon occurrence of a multiple-event condition(e.g., TIMER 1 expiring in FIG. 6H while TIMER 2 has not beendismissed), the electronic device 600 additionally causes output of thesecond audio notification. For example, the first audio notification andthe second audio notification can be concurrently output (e.g., layered,played back at the same time) or sequentially output (e.g., one followedby the other), or the like. By causing playback of two or more audionotifications, the electronic device indicates to a user that amultiple-event condition exists (e.g., is distinguishable from only oneof the audio notifications being output).

In some embodiments, a time-based notification is a timer type ofnotification. In some embodiments, a timer type of notification includesa notification condition that occurs when a determined length of timelapses (also referred to as a timer expiring). For example, a timer typeof notification causes output of a notification (e.g., audionotification) at a particular length of time after it begins, such asthirty seconds, five minutes, ten minutes, two hours, or the like. Insome embodiments, a timer can be paused (e.g., via user input). Forexample, if a timer is paused, the length of time ceases to progress(e.g., count down) until the timer is restarted (unpaused).

In some embodiments, a time-based notification is an alarm type ofnotification. In some embodiments, an alarm type of notificationincludes a notification condition that occurs upon reaching a particulartime of day (also referred to as an alarm expiring). In someembodiments, the time of day is on a particular date. For example, analarm type of notification causes output of a notification (e.g., audionotification) at a particular time (e.g., in the future), such as 4:32pm, 8:15 pm, 7:30 am, or the like. An alarm can be created in the sameway as a timer type of notification, as described above. For example,electronic device 600 can detect the voice input “HEY SIRI, SET AN ALARMFOR 6:32 PM” and, in response, set an alarm based on the notificationcondition 6:32 pm (e.g., occurrence of that time). In this example, oncethe time 6:32 pm arrives (e.g., the next time a clock of the devicereaches that time), the device causes output of an audio notification(e.g., a single-event or a multi-event notification). Thus, if the timewas 5:00 pm when the alarm was created, the alarm would cause an audionotification to be output approximately one hour and thirty-two minutesafter being created. Further, the notification condition of an alarm canbe a particular day or days (e.g., daily, weekdays). Thus, if theelectronic device detects the voice input “HEY SIRI, SET AN ALARM FOR6:32 PM ON WEDNESDAY” at 5:00 pm on a Monday, Sep. 21, 2020, theelectronic device would wait until 6:32 pm on the next Wednesday (Sep.23, 2020)(e.g., forty-nine hours and thirty-two minutes) untiloutputting the audio notification due to the occurrence of thecondition.

FIGS. 6I-6J illustrate exemplary interfaces for dismissing one or moretime-based notifications. FIG. 6I illustrates electronic deviceoutputting exemplary audio output 618 (which includes AUDIO NOTIFICATION2) due to the existence of a multiple-event condition—the expiration oftwo timers, TIMER 1 and TIMER 2, similar to the scenario shown in FIG.6H. In some embodiments, the electronic device (e.g., 600) receivesinput (e.g., voice input 620) representing a request to cease output ofan audio notification. For example, in FIG. 6I, electronic device 600detects voice input 620 that includes the words “HEY SIRI, STOP”.

In this example, audio output 618 is provided as an illustration of theaudio notification that is output in the scenario depicted, and is notintended to preclude the output of an audio identifier (e.g., a name)for a time-based notification in the given exemplary scenario. Forexample, audio output 608 can represent a simplified representation ofaudio output 622 (FIG. 6K) or audio output 624 (FIG. 6L). Techniques fordetermining whether to output an audio identifier are discussed ingreater detail below.

In some embodiments, in response to receiving input (e.g., 620)representing a request to cease output of an audio notification, theelectronic device (e.g., 600) ceases to output an audio notification(e.g., audio output 618 that includes AUDIO NOTIFICATION 2). Forexample, in FIG. 6J, the electronic device 600 has ceased output ofaudio output 618 (including AUDIO NOTIFICATION 2). As shown, device 600is no longer causing output of any audio notification (e.g., is silent).In some embodiments, in response to receiving input (e.g., 620)representing a request to cease output of an audio notification, theelectronic device (e.g., 600) dismisses one or more time-basednotifications whose corresponding notification conditions have occurred(e.g., and that have not yet been dismissed). For example, as shown instatus box 601 of FIG. 6J, both TIMER 1 and TIMER 2 have been dismissedas they are no longer depicted, standing in contrast to status box 601of FIG. 6I when both TIMER 1 and TIMER 2 were expired (e.g., had no timeremaining on each timer) but not dismissed.

In some embodiments, the occurrence of a second time-based notificationcauses a single-event audio notification to be replaced by amultiple-event audio notification. For example, in FIGS. 6G-6H, device600 is outputting AUDIO NOTIFICATION 1 because TIMER 2 has expired, andthen begins output of AUDIO NOTIFICATION 2 upon TIMER 1 expiring. Insome embodiments, in response to a request to cease output of an audionotification, the electronic device (e.g., 600) ceases output of thecurrent audio notification and does not resume output of another audionotification (e.g., because the device dismisses all expired time-basednotifications). For example, after changing from AUDIO NOTIFICATION 1(an exemplary single-event audio notification) to AUDIO NOTIFICATION 2(an exemplary multiple-event audio notification) in FIGS. 6G-6H,electronic device 600 does not resume output of AUDIO NOTIFICATION 1 inresponse to receiving input 620 in FIG. 6I. Rather, as shown in FIG. 6J,the device dismisses both time-based notifications and does not revertto a single-event notification scenario.

In some embodiments, the input representing a request to cease output ofan audio notification is a touch input. For example, device 600 receivesan input via touch-sensitive surface (e.g., 580D). For example, whileoutputting an audio notification, a detected touch gesture (e.g., a tap,a tap and hold) on a touch-sensitive surface of device 600 can representthe request to cease output of an audio notification, as describedabove.

In some embodiments, in response to a request to cease output of anaudio notification, the electronic device (e.g., 600) dismisses fewerthan all of the time-based notifications that have expired. In someembodiments, the electronic device dismisses one notification perrequest to cease output of an audio notification. For example, a singletap on touch-sensitive surface of device 600 in the scenario depicted inFIG. 6H (outputting exemplary multiple-event audio notification AUDIONOTIFICATION 2) can dismiss only one time-based notification that isgoing off at a time (e.g., sequentially, such as in order of whichtime-based notification expired first; in this example, TIMER 2). Insuch case, if TIMER 2 was dismissed in response to a first input, theelectronic device would have one remaining time-based notification thathas not been dismissed and that has expired (TIMER 1), and thus canbegin output of a single-event audio notification (e.g., AUDIONOTIFICATION 2). A second input (e.g., voice input, touch ontouch-sensitive surface) can cause device 600 to then dismiss TIMER 1.

FIGS. 6K-6L illustrate exemplary techniques for causing output of anaudio identifier identifying a time-based notification. In someembodiments, the electronic device (e.g., 600) causes output of an audioidentifier that identifies a time-based notification. For example, inresponse to a notification condition for a time-based notificationcondition occurring, the electronic device can output an audioidentifier (e.g., a text-to-speech dictation output of a name or otheridentifying information) for the corresponding time-based notification.For example, in FIG. 6K, TIMER 1 has the name “TEN MINUTE”, andelectronic device is outputting audio output 622 which includes thetext-to-speech dictation “TEN MINUTE AND FIVE MINUTE TIMERS”. Thus,audio output 622 includes the audio identifier “TEN MINUTE” thatidentifies that the timer named TEN MINUTE is currently going off. Insome embodiments, the electronic device (e.g., 600) causes output ofaudio identifiers that identify a plurality of time-based notifications.For example, audio output 622 also includes the audio identifier “FIVEMINUTE” that identifies that the timer named FIVE MINUTE is currentlygoing off, in addition to identifying that the timer named TEN MINUTE isgoing off.

In some embodiments, the electronic device (e.g., 600) outputs an audionotification (e.g., one or more) and an audio identifier (e.g., one ormore) in a predetermined pattern. For example, as shown in FIG. 6K, anaudio notification (AUDIO NOTIFICATION 2) is output twice, followed byoutput of audio identifiers (“TEN MINUTE AND FIVE MINUTE TIMERS”). Thus,in this example, the predetermined pattern is two repetitions of anaudio notification (AUDIO NOTIFICATION 2) followed by a single output ofaudio identifiers (“TEN MINUTE AND FIVE MINUTE TIMERS”).

In some embodiments, the predetermined pattern repeats until thenotification(s) is/are dismissed. In this example, the patternrepeats—as shown in audio output 622, the audio notification “AUDIONOTIFICATION 2” is output another two times after the audio identifiers(e.g., which will be followed by output of the audio identifiers “TENMINUTE AND FIVE MINUTE TIMERS”), and so on.

In some embodiments, the predetermined pattern changes after theelectronic device outputs the pattern one or more times without thenotification(s) being dismissed. For example, as shown in FIG. 6L, thepredetermined pattern has changed to four repetitions of an audionotification (AUDIO NOTIFICATION 2) followed by the output of audioidentifiers (“TEN MINUTE AND FIVE MINUTE TIMERS”), as indicated by audiooutput 624. Thus, the time between output of the audio identifiers hasincreased (e.g., from two to four repetitions of the audionotification). In this example, the predetermined pattern changed afterbeing output twice. In some embodiments, the predetermined patternchanges two or more times. For example, after another number (e.g., two,or some other number) of repetitions of the modified pattern, thepredetermined pattern can change again to eight repetitions of an audionotification (e.g., AUDIO NOTIFICATION 2) followed by the output ofaudio identifiers (e.g., “TEN MINUTE AND FIVE MINUTE TIMERS”), and thento sixteen, and so on.

FIGS. 6M-6N illustrate exemplary interfaces for providing a visualindication of a single-event and a multiple-event condition. In someembodiments, the electronic device provides a visual indication that asingle-event condition exists. In some embodiments, the visualindication is provided using one or more light emitting devices (e.g.,580E) (e.g., a light-emitting diode, a display screen). For example, inFIG. 6M, indicator 600A (a plurality of LEDs) are shown outputting lightin a first color (e.g., indicated visually in FIG. 6M by the pattern ineach LED) concurrently with outputting AUDIO NOTIFICATION 1, anexemplary single-event audio notification. As shown in FIG. 6M, statusbox 601 illustrates that TIMER 2 has expired, but TIMER 1 still has 0:01(one second) remaining.

In some embodiments, the electronic device provides a visual indicationthat a multiple-event condition exists. In some embodiments, the visualindication is provided using one or more light emitting devices (e.g., alight-emitting diode, a display screen). For example, in FIG. 6N,indicator 600A (a plurality of LEDs) are shown outputting light in asecond color (e.g., indicated visually in FIG. 6N by the pattern in eachLED) concurrently with outputting AUDIO NOTIFICATION 2, an exemplarymultiple-event audio notification. In this example, the second color ofFIG. 6N is different than the first color of FIG. 6M (e.g., depicted asa different pattern in each LED of indicator 600A). Thus, based on thedifferent visual indicators for each event condition, a user could tellthat a multiple-event condition exists in contrast to a single-eventcondition. As shown in FIG. 6N, status box 601 illustrates that bothTIMER 1 and TIMER 2 have expired and have not been dismissed. It shouldbe appreciated that other visual indications can be used in addition toor instead of different colors for the single and multiple-eventconditions. For example, the device can output (e.g., using indicator600A) different animated patterns (e.g., swirling, pulsing, and/orsizing based on the number of time-based notifications going off),identifying text and/or numbers, or other visual indications that can bedifferentiated from one another.

In some embodiments, a multiple-event audio notification is amultiple-event audio notification for a first type of time-basednotification. When multiple time-based notifications have expired andare a first type of time-based notification, the audio notificationoutput is a multiple-event audio notification for the first type. Insome embodiments, a multiple-event audio notification is amultiple-event audio notification for a second type of time-basednotification. When multiple time-based notifications have expired andare a second type of time-based notification, the audio notificationoutput is a multiple-event audio notification for the second type. Insome embodiments, the multiple-event audio notification for the firsttype and the multiple-event audio notification for the second type aredifferent. For example, they can be different media entities that sounddifferent when played back, thus providing an indication of the type oftime-based notifications going off.

FIG. 6O illustrates an exemplary technique for determining which type ofmultiple-event audio notification to output when there are multipletypes of multiple-event audio notifications. The rows of table 626 inFIG. 6O respectively illustrate one of three exemplary scenarios wheretwo notifications (NOTIFICATION 1 and NOTIFICATION 2) have expired andhave not been dismissed. In some embodiments, the electronic device iscapable of setting a first type of time-based notification and a secondtype of time-based notification. For example, a first type can be atimer type of notification and a second type can be an alarm type ofnotification. In another example, the first type is alarm and the secondtype is timer. Accordingly, when at least two notifications of the firsttype have expired and have not been dismissed, and no notifications ofthe second type have expired, the electronic device 600 causes output ofa multiple-event audio notification for the first type of time-basednotification. For example, row 626A in table 626 illustrates that whenNOTIFICATION 1 is a first type and a NOTIFICATION 2 is also the firsttype, the audio notification output is a multiple-event audionotification for the first type. Likewise, when at least twonotifications of the second type have expired and have not beendismissed, and no notifications of the first type have expired, theelectronic device 600 causes output of a multiple-event audionotification for the second type of time-based notification. Forexample, row 626C in table 626 illustrates that when NOTIFICATION 1 is asecond type and a NOTIFICATION 2 is also the second type, the audionotification output is a multiple-event audio notification for thesecond type.

In some embodiments, when at least one of the first type and at leastone of the second type of time-based notification have expired and havenot been dismissed, the electronic device (e.g., 600) causes output ofthe multiple-event notification for one of the first type or the secondtype of time-based notifications. For example, the multiple-event audionotification for an alarm type of notification can take priority overthe multiple-event audio notification for a timer type of notification.Thus, when at least one alarm has expired and at least one othertime-based notification has expired (e.g., alarm or timer), theelectronic device 600 causes output of the multiple-event audionotification corresponding to the alarm type of notification. Forexample, row 626B in table 626 illustrates that when NOTIFICATION 1 is afirst type (e.g., a timer) and a NOTIFICATION 2 is the second type(e.g., an alarm), the audio notification output is a multiple-eventaudio notification for the second type (e.g., an alarm). This is useful,for instance, where one type of time-based notification has prioritysuch that notifying the user that at least one instance of that type ofnotification is preferable. Thus, an alarm type can be more importantthan a timer, and thus the multiple-event audio notification for thealarm takes precedent when an alarm is one of at least two notificationsgoing off concurrently.

FIGS. 7A-7B is a flow diagram illustrating a method for outputtingmultiple-event audio notifications using an electronic device inaccordance with some embodiments. Method 700 is performed at a device(e.g., 100, 300, 500, 580). Some operations in method 700 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for outputtingmultiple-event audio notifications. The method reduces the cognitiveburden on a user for determining whether a multiple-event conditionexists, thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to determine whethera multiple-event condition exists faster and more efficiently conservespower and increases the time between battery charges.

The electronic device (e.g., 600) receives (702) information (e.g.,audio input 604) representing a first time-based notification condition(e.g., a timer length or an alarm time). For example, device 600receives voice input 604 in FIG. 6A, which includes the exemplary firsttime-based notification condition: a timer length of ten minutes.

The electronic device (e.g., 600) sets (704) a first time-basednotification (e.g., TIMER 1 in FIG. 6B) based on the first time-basednotification condition (e.g., length often minutes).

In response to a determination (706) that the first time-basednotification condition has occurred (e.g., timer expires, alarm timearrives), and in accordance with a determination that the electronicdevice (e.g., 600) is not currently causing output (e.g., as shown inFIG. 6C) of an audio notification based on at least one time-basednotification other than the first time-based notification (e.g., TIMER 1in FIG. 6C), the electronic device (e.g., 600) causes (708) output(e.g., via a speaker of the electronic device, or one or more otherassociated/connected devices/speakers) of a first audio notification(e.g., AUDIO NOTIFICATION 1 in audio output 608 of FIG. 6D)(e.g., asingle-event audio notification). For example, the electronic device isnot currently outputting an audio notification for another expiredtime-based notification (e.g., timer or alarm) when the first time-basednotification condition occurs.

In response to the determination (706) that the first time-basednotification condition has occurred (e.g., timer expires, alarm timearrives), and in accordance with a determination that the electronicdevice (e.g., 600) is currently causing output (e.g., as shown in FIG.6G) of the audio notification (e.g., AUDIO NOTIFICATION 1 in FIG. 6G)based on at least one time-based notification (e.g., TIMER 2 in FIG. 6G)other than the first time-based notification (e.g., TIMER 1 in FIG. 6G),the electronic device (e.g., 600) causes (710) output of a second audionotification (e.g., AUDIO NOTIFICATION 2 in FIG. 6H) (e.g., amultiple-event audio notification) different from the first audionotification.

Outputting a second audio notification different from the first audionotification when an electronic device is already causing output of anaudio notification provides the user with audio feedback about thenumber of time-based notification conditions that have occurred.Providing improved audio feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, after causing output of the second audionotification (e.g., and dismissal thereof), the electronic device sets asubsequent time-based notification based on the same first time-basednotification condition as the first time-based notification. Forexample, another ten-minute timer is created after TIMER 1 of FIG. 6Dhas expired and has been dismissed. As another example, the device 600sets a first alarm for the time of day 6:32 pm, and a subsequent alarmfor 6:32 pm (which will occur on the subsequent day as the first alarm).In response to a determination that the first time-based notificationcondition has occurred the first time, the electronic device (e.g., 600)causes output of the second audio notification. For example, the firsttime that the first time-based notification condition occurs, the deviceis currently causing output of an audio notification (e.g., anotheralarm or timer has expired and is causing audio output), so the devicecauses output of the second audio notification (e.g., AUDIO NOTIFICATION2, an exemplary multiple-event audio notification). In response to adetermination that the first time-based notification condition hasoccurred the second time, the electronic device (e.g., 600) causesoutput of the first audio notification. For example, the second timethat the first time-based notification condition occurs (e.g., when usedto set a subsequent time-based notification), the device is notcurrently causing output of an audio notification (e.g., another alarmor timer has not expired and causing audio output), so the device causesoutput of the first audio notification (e.g., AUDIO NOTIFICATION 1, anexemplary single-event audio notification). The audio notification thatis output (e.g., AUDIO NOTIFICATION 1 or AUDIO NOTIFICATION 2) candepend on the state of the electronic device (e.g., 600) when thecorresponding time-based notification condition expires. Thus, a secondtime-based notification can cause output of a different audionotification than a first time-based notification that are both setbased on the same time-based notification condition because the state ofthe device at the time a time-based notification condition expires canaffect which audio notification a device outputs. Accordingly, for thesame time-based notification condition, the audio notification that isoutput upon occurrence of the condition can depend on whether one ormore other time-based notification conditions have occurred and arecausing output of an audio notification.

In some embodiments, the audio notification based on at least onetime-based notification other than the first time-based notification isthe first audio notification (e.g., exemplary single-event audionotification AUDIO NOTIFICATION 1 in audio output 614, which device 600is causing output of as shown in FIG. 6G). Further in accordance withthe determination that the electronic device (e.g., 600) is currentlycausing output of the audio notification (e.g., AUDIO NOTIFICATION 1, asshown in FIG. 6G) based on at least one time-based notification (e.g.,TIMER 2 in FIG. 6G) other than the first time-based notification (e.g.,TIMER 1 in FIG. 6O), the electronic device (e.g., 600) ceases (712) tocause output of the first audio notification. For example, in FIG. 6H,device 600 has ceased causing output of AUDIO NOTIFICATION 1. Thus, inthis example, the first notification condition occurring (expiration ofTIMER 1 in FIGS. 6G-6H) causes device 600 to stop playing a single-eventnotification because a multiple-event condition now exists.

Ceasing to cause output of a first audio notification when an electronicdevice enters a multiple-event condition and begins causing output of asecond audio notification provides the user with audio feedback aboutthe number of time-based notification conditions that have occurred.Providing improved audio feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the electronic device causes output of both thefirst and second audio notifications (e.g., sequentially, or layered) inaccordance with the determination that the electronic device iscurrently causing output of the audio notification based on at least onetime-based notification other than the first time-based notification.For example, the first and second audio notifications can be played backto back (sequentially), played concurrently (layered), or somecombination thereof.

In some embodiments, causing output of the second audio notificationcomprises causing output of the second audio notification to begin uponceasing to cause output of the first audio notification. For example,the output of the second audio notification cuts off the first audionotification (e.g., in the middle of playback of the first audionotification where it has a length of time). In some embodiments, thedevice waits for the end of the first audio notification (e.g., where ithas a length of time) before causing output of the second audionotification. For example, if the first audio notification is a mediaentity having some length of time when played back, electronic device600 waits until the end of the length of time (e.g., plays back thefirst audio notification for the full length) before beginning output ofthe second audio notification.

In some embodiments, receiving the information representing the firsttime-based notification condition comprises receiving a voice input(e.g., 604) representing a request to set the first time-basednotification (e.g., “HEY SIRI, SET A TIMER FOR TEN MINUTES”), whereinthe voice input includes the information representing the firsttime-based notification condition (e.g., “TIMER FOR TEN MINUTES” invoice input 604). In some examples, the electronic device transcribes(or causes to be transcribed via a connection to one or more otherdevices, such as one or more cloud-based servers) the voice input (e.g.,using a speech-to-text algorithm) and determines the informationrepresenting the first time-based notification condition from thetranscription.

In some embodiments, receiving the information representing the firsttime-based notification condition comprises receiving data from a secondelectronic device (e.g., a device including one or more features ofdevices 100, 300, 500, 580), connected to the electronic device (e.g.,600), representing a request to set the first time-based notification,wherein the data includes the information representing the firsttime-based notification condition (e.g., timer for ten minutes). Forexample, a second device can be a smartphone that is used to input atime-based notification for a timer or alarm to be set, which is thencommunicated to device 600.

In some embodiments, while causing output of the second audionotification (e.g., a multi-event audio notification) (e.g., audiooutput 618 of AUDIO NOTIFICATION 2, as shown in FIG. 6I), the electronicdevice (e.g., 600) receives (714) an input (e.g., voice input 620)representing a request to cease audio notification output (e.g., “HEYSIRI, STOP”). In response to receiving the input representing therequest to cease audio notification output, the electronic device (e.g.,600) ceases (716) to cause output of the second audio notification(e.g., as shown in FIG. 6J). For example, a single input dismisses alltime-based notifications that are going off concurrently and that havenot yet been dismissed. In some embodiments, the input representing therequest to cease audio notification output is a voice input (e.g., voiceinput 620). In some embodiments, the input representing the request tocease audio notification output is a touch input (e.g., a touch gestureon a touch-sensitive surface of device 600).

In some embodiments, a single input dismisses only time-basednotifications of the same type. For example, the single input candismiss all timers concurrently going off but not any alarms that arealso concurrently going off, or can dismiss all alarms concurrentlygoing off but not any timers that are also concurrently going off.

In some embodiments, discrete user inputs cause the electronic device(e.g., 600) to sequentially dismiss each notification of a plurality ofnotifications that are concurrently going off. For example, if twotime-based notifications are concurrently going off, a first inputdismisses a first one, and electronic device continues to cause outputof an audio notification based on the remaining non-dismissednotification (the second one). A subsequent, second input dismisses theremaining non-dismissed (second) notification, and the device thenceases audio notification output because all time-based notificationshave now been dismissed. In some embodiments, the audio notificationbeing output by the device changes from a multiple-event audionotification to a single-event audio notifications between inputs. Forexample, in response to the first input that dismisses a time-basednotification that results in the device 600 going from a multiple-eventcondition to a single-event condition (e.g., that leaves only onetime-based notification that is going off and has not been dismissed),then the audio notification output changes from a multiple-event audionotification to a single-event audio notification.

In some embodiments, prior to the determination that the firsttime-based notification condition has occurred: the electronic device(e.g., 600) sets a second time-based notification (e.g., TIMER 2 of FIG.6F) based on a second time-based notification condition (e.g., fiveminute timer); and while the electronic device is not currently causingoutput of an audio notification based on at least one time-basednotification other than the second time-based notification (e.g., thedevice is not currently outputting another time-based notification(e.g., timer or alarm) when the second time-based notification conditionoccurs), and in response to a determination that the second time-basednotification condition has occurred (e.g., timer expires, alarm timearrives) (e.g., TIMER 2 expires as shown in FIG. 6G), the electronicdevice (e.g., 600) causes output of the first audio notification (e.g.,a single-event audio notification)(e.g., AUDIO NOTIFICATION 1 in audiooutput 614 as shown in FIG. 6G, an exemplary single-event audionotification). Further in response to the determination (706) that thefirst time-based notification condition has occurred, and in accordancewith the determination that the electronic device is currently causingoutput of the audio notification (e.g., AUDIO NOTIFICATION 1 in audiooutput 614, as shown in FIG. 6G, an exemplary single-event audionotification) based on at least one time-based notification other thanthe first time-based notification, the electronic device (e.g., 600)ceases to cause output of the first audio notification (e.g., AUDIONOTIFICATION 1 in audio output 614, as shown in FIG. 6G), wherein thefirst time-based notification occurs while the electronic device iscurrently causing output of the first audio notification based on thesecond time-based notification (e.g., audio output 614 of FIG. 6G). Forexample, device 600 ceases output of a single-event audio notification(e.g., AUDIO NOTIFICATION 1 in audio output 614, as shown in FIG. 6G, anexemplary single-event audio notification), in addition to causingoutput of a multiple-event audio notification (e.g., AUDIO NOTIFICATION2 in audio output 616, as shown in FIG. 6H, an exemplary multiple-eventaudio notification). For example, when a single-event condition haschanged to a multiple-event condition by virtue of the first time-basednotification condition expiring, the audio output changes from asingle-event audio notification to a multiple-event audio notification.

In some embodiments, while the electronic device is currently causingoutput of the second audio notification (e.g., as shown in FIG. 6I),wherein the first time-based notification condition and the secondtime-based notification condition have occurred (e.g., TIMER 1 and TIMER2 have expired, as shown in status box 601 of FIG. 6I), and wherein thefirst time-based notification (e.g., TIMER 1 of FIG. 6I) and the secondtime-based notification (e.g., TIMER 2 of FIG. 6I) have not beendismissed (e.g., TIMER 1 and TIMER 2 have not been dismissed, as shownin status box 601 of FIG. 6I), the electronic device (e.g., 600)receives the input (e.g., 620) representing the request to cease audionotification output. Further in response to receiving the input (e.g.,620) representing the request to cease audio notification output: theelectronic device (e.g., 600) dismisses the first time-basednotification and the second time-based notification (e.g., TIMER 1 andTIMER 2 have been dismissed, as shown in status box 601 of FIG. 6J),wherein upon ceasing to cause output of the second audio notificationthe electronic device does not begin to cause output of the first audionotification (e.g., as shown in FIG. 6J).

Ceasing to cause output of a second audio notification and dismissingconcurrently expired time-based notifications when an electronic deviceis in a multiple-event condition reduces the number of inputs needed todismiss concurrently expired time-based notifications. Reducing thenumber of inputs needed to perform an operation enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first time-based notification conditionincludes one or more of: a first type of notification condition thatoccurs upon expiration of a determined length of time (e.g., a timer);and a second type of notification condition that occurs upon arrival ofa determined time of day (e.g., an alarm).

In some embodiments, the at least one time-based notification other thanthe first time-based notification is a third time-based notification(e.g., TIMER 2 in FIG. 6K), and wherein the third time-basednotification condition was previously set by the electronic device basedon a third time-based notification condition (e.g., five-minute timer).While causing output of the second audio notification (e.g., AUDIONOTIFICATION 2 in audio output 622 of FIG. 6K), and subsequent to thedetermination that the first time-based notification condition hasoccurred (e.g., TIMER 1 is expired in FIG. 6K) and a determination thatthe third time-based notification condition has occurred (e.g., TIMER 2is expired in FIG. 6K), and while the first time-based notification andthe third time-based notification have not been dismissed (e.g., TIMER 1and TIMER 2 have not been dismissed in FIG. 6K): the electronic device(e.g., 600) causes (718) output of audio identifiers (e.g., names) thatidentify the first time-based notification and the third time-basednotification (e.g., audio output 622 includes the identifiers TEN MINUTEand FIVE MINUTE in the text-to-speech output of the statement “TENMINUTE AND FIVE MINUTE TIMERS” in FIG. 6K). In some embodiments, anaudio identifier (e.g., the name TEN MINUTE) that identities atime-based notification is a name given to the time-based notificationvia user input. For example, if the user names a timer “DINNER” then theelectronic device can cause output of a dictation that says “DINNERTIMER” upon that timer expiring. In some embodiments, an audioidentifier that identifies a time-based notification is a time valueassociated with a notification condition of the time-based notification.In some embodiments, the audio identifier is a time value by default ifa name is not otherwise specified for the time-based notification (e.g.,specified by user input setting the name). For example, an audioidentifier (e.g., name) for a ten-minute timer that was not named can beset by default to “ten minute” based on the time value of thenotification condition, and upon expiration the audio identifier that isannounced is “TEN MINUTE TIMER”.

Outputting audio identifiers that identify time-based notifications thathave expired provides the user with audio feedback about the identity ofwhich time-based notifications have expired. Providing improved audiofeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, causing output of the second audio notification andcausing output of the audio identifiers comprises causing output of thesecond audio notification (e.g., AUDIO NOTIFICATION 2 in FIG. 6K) andthe audio identifiers (e.g., “TEN MINUTE AND FIVE MINUTE TIMERS” in FIG.6K) in a predetermined pattern that includes causing output of thesecond audio notification a first predetermined number of times (e.g.,two times as shown in FIG. 6K) and causing output of the audioidentifiers that identify the first time-based notification and thethird time-based notification a second predetermined number of times(e.g., one time as shown in FIG. 6K). For example, as shown in FIG. 6K,audio output 622 includes a predetermined pattern in which an audionotification (AUDIO NOTIFICATION 2) is output twice, followed by outputof an audio identifier (two in this example, “TEN MINUTE AND FIVE MINUTETIMERS”). In some embodiments, the second audio notification is outputthe first predetermined number of times, followed by the audioidentifiers. In some embodiments, the device outputs the audioidentifiers followed by the second audio notification.

In some embodiments, the electronic device (e.g., 600) causes output ofthe predetermined pattern to repeat (e.g., until dismissal of thenotifications or expiration of a predetermined amount of time (e.g., 15minutes)). For example, in FIG. 6K, the pattern repeats (e.g., AUDIONOTIFICATION 2 is shown being output another two times after the audioidentifiers “TEN MINUTE AND FIVE MINUTE TIMERS” are announced the firsttime).

In some embodiments, the first predetermined number of times (e.g., twotimes) increases to a third predetermined number of times (e.g., fourtimes) after the electronic device has caused output of thepredetermined pattern a fourth predetermined number of times (e.g.,after the pattern has repeated two times). For example, in FIG. 6L, thenumber of times that the audio notification AUDIO NOTIFICATION 2 isoutput during one repetition of the predetermined pattern has increasedto four. For example, a predetermined pattern can include: audionotification is output X number of times (e.g., 2) before voiceassistant output that includes audio identifier(s), then the patternchanges to audio notification being output Y number of times (e.g., 4)followed by the audio identifier output after the pattern has beenoutput Z number times (e.g., 2). For example, the pattern can be: (audionotification, audio notification, announce audio identifier), (audionotification, audio notification, announce audio identifier), (audionotification (four times), announce audio identifier) and repeat until atimeout (e.g., fifteen minutes). In some embodiments, after thepredetermined pattern changes to Y number of times (e.g., 4), it cansubsequently again change to N number of times (e.g., 8) after one ormore cycles (e.g., Z number of times). In some embodiments, audio output(e.g., including audio notification and/or audio identifier)automatically ceases after a period of time (e.g., times out afterfifteen minutes).

In some embodiments, the first audio notification is a single-eventaudio notification that indicates occurrence of a time-basednotification condition of a single time-based notification that has notbeen dismissed (e.g., a single-event condition), and the second audionotification is a multiple-event audio notification that indicates theoccurrence of time-based notification conditions of multiple time-basednotifications that have not been dismissed (e.g., a multiple-eventcondition).

Outputting a first audio notification that is a single-event audionotification different from a second audio notification that is amultiple-event audio notification provides the user with audio feedbackabout the number of time-based notification conditions that haveoccurred. Providing improved audio feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in accordance with a determination that the atleast one time-based notification includes a third type of time-basednotification (e.g., an alarm) or that the first time-based notificationis the third type of time-based notification (e.g., an alarm), thesecond audio notification is a first multiple-event audio notification(e.g., a multiple-event audio notification for an alarm type oftime-based notification). For example, in FIG. 6O, rows 626B and 626C oftable 626 illustrate that if at least one time-based notification goingoff NOTIFICATION 1 (e.g., an exemplary first time-based notification)and NOTIFICATION 2 (e.g., an exemplary at least one time-basednotification) is the SECOND type (e.g., an exemplary third type oftime-based notification), then the multiple-event audio notificationoutput is for the SECOND type. In accordance with a determination thateach of the at least one time-based notification is a fourth type oftime-based notification (e.g., a timer) different from the third type(e.g., an alarm) and that the first time-based notification is thefourth type of time-based notification (e.g., a timer), the second audionotification is a second multiple-event audio notification (e.g., amultiple-event audio notification for a timer type of time-basednotification) different from the first multiple-event audionotification. For example, in FIG. 6O, row 626A of table 626 illustratesthat if the only time-based notifications already going off NOTIFICATION1 and NOTIFICATION 2 are both the FIRST type (e.g., an exemplary fourthtype of time-based notification), then the multiple-event audionotification output is for the FIRST type. In some embodiments, thethird type is an alarm type notification and the fourth type is a timertype notification. In some embodiments, the third type is a timer typenotification and the fourth type is an alarm type notification.

In some embodiments, while causing output of the first audionotification (e.g., audio output 614 including AUDIO NOTIFICATION 1 asshown in FIG. 6M), the electronic device (e.g., 600) causes output of afirst visual indication (e.g., 600A as shown in FIG. 6M). While causingoutput of the second audio notification (e.g., audio output 616including AUDIO NOTIFICATION 2 as shown in FIG. 6N), the electronicdevice (e.g., 600) causes output of a second visual indication (e.g.,600A as shown in FIG. 6N) different from the first visual indication.

In some embodiments, the first audio notification and the first visualindication correspond to each other, and the stimulus that causes theoutput of the first audio notification also causes the outputting of thefirst visual indication (e.g., without causing output of the secondvisual indication). In some examples, the second audio notification andthe second visual indication correspond to each other, and the stimulusthat causes the output of the second audio notification also causes theoutputting of the second visual indication (e.g., without causing outputof the first visual indication).

Outputting a first visual indication while causing output of a firstaudio notification and outputting a second visual indication whilecausing output of a second audio notification provides the user withvisual feedback about the number of time-based notifications that haveexpired. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

Note that details of the processes described above with respect tomethod 700 (e.g., FIGS. 7A-7B) are also applicable in an analogousmanner to the methods described below. For example, method 900optionally includes one or more of the characteristics of the variousmethods described above with reference to method 700. For example, thetechnique for determining the type of audio notification to output canbe combined with the technique for determining whether to output anaudio identifier. For brevity, these details are not repeated below.

FIGS. 8A-8O illustrate exemplary user interfaces and techniques foroutputting audio identifiers for time-based notifications, in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIGS. 9A-9B. 10241J FIGS. 8A-8F illustrate exemplary techniques forannouncing an audio identifier that identities an audio notification(e.g., that has expired). As illustrated herein, an electronic devicethat is capable of setting multiple time-based notifications that areconcurrently active (e.g., set, not dismissed, and expired) can, undercertain conditions, announce the name of one or more time-basednotifications that have expired in order to provide useful informationregarding the cause of an audio notification output.

FIGS. 8A-8B illustrate an exemplary technique for causing an electronicdevice to set a time-based notification. In FIGS. 8A-8N, a device statusbox 801 indicates a status of the state of electronic device 600 and isprovided as a visual indication of a status of any time-based indicatorsthat are set (e.g., in memory of device 600) in the respective examplescenario depicted in each respective figure. Like device status box 601,device status box 801 is provided merely as a visual aid, and is notnecessarily displayed by a device (e.g., 600). Additionally, unlessotherwise noted in a figure or herein, device status box 801 indicatesthe status of device 600 after any voice input and audio output depictedin the respective figure.

Turning to FIG. 8A, as noted in device status box 801, no time-basednotifications are set (e.g., in memory of device 600) before voice input804. That is, in FIG. 8A, box 801 identifies that no time-basednotifications are set (“NONE”) before the device 600 receives voiceinput command 804.

In some embodiments, an electronic device (e.g., 600) receivesinformation (e.g., 804) representing a time-based notification condition(e.g., ten-minute length). In some embodiments, the information isreceived as a voice input. For example, as illustrated in FIG. 8A,device 600 detects (e.g., via one or more microphones, such as inputmechanism 588) voice input 804 provided by user 602 that includesinformation representing a time-based notification condition, a lengthof time minutes for a timer. In some embodiments, the informationrepresenting the time-based notification condition is part of a requestto create a time-based notification. In this example, the voice input804 includes the phrase: “HEY SIRI, SET A TIMER FOR TEN MINUTES”. Thus,the voice input 804 includes the following information: a timer shouldbe set (an exemplary request to set a timer type time-basednotification), the timer having a length often minutes (an exemplarytime-based notification condition).

As described above, a time-based notification can be an alarm. Forexample, in response to a voice input that includes “HEY SIRI, SET ANALARM FOR TEN MINUTES”, electronic device 600 can set an alarm for thetime of day (e.g., 6:40 pm) that is ten minutes from the current time ofday (e.g., 6:30 pm). In some embodiments, in response to a request tocreate an alarm, the electronic device (e.g., 600 outputs anacknowledgement that includes a time-based notification condition. Forexample, after setting the alarm, device 600 can output “OK, I'VE SET ANALARM FOR SIX FORTY P.M.” Thus, even though the voice input indicatedthat the alarm should be for the time of day in ten minutes, the deviceindicates the actual notification condition, which is the occurrence of6:40 pm. Likewise, an acknowledgement that includes the time-basednotification condition can also be output when the input includes thetime-based notification condition, such as in response to “HEY SIRI, SETAN ALARM FOR SIX FORTY P.M.”

FIG. 8B illustrates an exemplary response to receiving informationrepresenting a time-based notification condition (e.g., a request to seta time-based notification). In some embodiments, the electronic device(e.g., 600) sets a first time-based notification based on the receivedinformation representing the time-based notification condition. Forexample, in response to detecting voice input 804, electronic device 600sets a timer having a notification condition that occurs when tenminutes have passed. As shown in FIG. 8B, in response to voice input804, electronic device 600 has set a timer (TIMER 1) named “TEN MINUTE”,as indicated by device status box 801 in FIG. 8B. Device status box 801in FIG. 8B also indicates the time remaining on the timer named “TENMINUTE”, which is 9:59 (nine minutes and fifty-nine seconds). In thisexample, one second has elapsed since creation of the “TEN MINUTE”timer, which had an original duration of ten minutes. Additionally, asshown in FIG. 8B, in response to detecting voice input 804 (FIG. 8A)device 600 outputs audio output 806, which is an acknowledgement ofvoice input 804 and indicates that the electronic device set aten-minute timer.

In some embodiments, in response to occurrence of a time-basednotification condition of a time-based notification, the electronicdevice (e.g., 600) causes output of a name of the time-basednotification. In some embodiments, the device causes output of the namein accordance with a determination that a name output condition is met.In some embodiments, the device causes output of the name in accordancewith a determination that one or more name output conditions in a set ofname output conditions is met. For example, if at least one name outputcondition in the set of name output conditions is met, an electronicdevice (e.g., 600) causes output of an audio identifier (e.g., name) fora time-based notification (e.g., that has expired). In another example,the device can require that more than one or all name output conditionsin the set of name output conditions are met in order to cause output ofthe name of the time-based notification.

FIG. 8C illustrates an exemplary audio output when a name outputcondition is not met. For example, in FIG. 8C, electronic device 600causes output of audio output 808. Audio output 808 includes output ofan audio notification (illustrated by the text “*OUTPUTTING AUDIONOTIFICATION*”) but does not output a name of the time-basednotification that has expired. In FIG. 8C, the TIMER 1 named “TENMINUTE” has expired, as shown in status box 801. Thus, for example,instead of outputting an audio notification and a name in apredetermined pattern as described above (e.g., audio notificationtwice, followed by the name), device 600 outputs the audio notificationcontinuously (e.g., the audio notification is shown three times in a rowin audio output 808, followed by an ellipsis “ . . . ” indicating thatthe output continues). In this example, the audio notification in audiooutput 808 is a single-event audio notification associated with thetimer type of time-based notification, because only a single time-basednotification is going off, in accordance with embodiments describedabove.

FIGS. 8D-8F illustrate an exemplary audio output when a name outputcondition is met. Turning to FIG. 8D, the TIMER 1 named “TEN MINUTE”that was set in FIG. 8B is active (e.g., set and not expired), and nowhas 8:13 (eight minutes and thirteen seconds) remaining before device600 receives voice input 810. In FIG. 8D, the user 602 provides voiceinput 810 representing a request to create a new timer. Voice input 810includes the text “HEY SIRI, SET A TIMER FOR FIFTEEN MINUTES”. Device600 detects voice input 810 and in response creates a timer, as shown inFIG. 8E.

In FIG. 8E, device 600 has set TIMER 2 named “FIFTEEN MINUTE” inresponse to voice input 810. For example, as shown in status box 801 ofFIG. 8E, the FIFTEEN MINUTE timer has 14:59 (fourteen minutes andfifty-nine seconds) remaining (of an original length of fifteenminutes), while the TEN MINUTE timer (TIMER 1) has elapsed four secondssince before voice input 810 (FIG. 8D) and now has 8:09 (eight minutesand nine seconds) remaining. Also shown in FIG. 8E, electronic device600 outputs acknowledgement 812 (“FIFTEEN MINUTE TIMER, STARTING NOW”).

Turning to FIG. 8F, an exemplary audio output when a name outputcondition is met is illustrated. In FIG. 8F, electronic device outputsaudio output 814, which includes output of an audio notification(illustrated by the text “OUTPUTTING AUDIO NOTIFICATION*”) and output(e.g., a text-to-speech dictation) of a name of the timer that hasexpired (illustrated by the text “TEN MINUTE TIMER”).

In some embodiments, a name output condition includes a condition thatis met when at least one other time-based notification is active when afirst time-based notification's notification condition occurs. Forexample, as shown in FIG. 8F, the TEN MINUTE timer has expired, but theFIFTEEN MINUTE timer is still active (e.g., has been previously set andhas not expired or been dismissed or deleted). Thus, when thenotification condition for the TEN MINUTE TIMER occurs (ten minuteselapse), the FIFTEEN MINUTE timer has 6:50 (six minutes and fiftyseconds) remaining—for example, the same time differential that existedbetween the timers in FIG. 8E—which is the amount shown in status box801 of FIG. 8F. Thus, in FIG. 8F, the name output condition that atleast one other time-based notification is active (FIFTEEN MINUTE timer)when a first time-based notification's notification condition occurs(TEN MINUTE timer) would be met. Accordingly, in FIG. 8F, audio output814 includes output of the name of the time-based notification that iscurrently going off, the text-to-speech dictation “TEN MINUTE TIMER” inaddition to output of an audio notification. Audio output 814 is outputin a predetermined pattern, as described above (e.g., output of theaudio notification twice, followed by output of the audio identifier,after which the pattern repeats). Also, in this example, the audionotification is a single-event audio notification for the timer type oftime-based notification, because only a single time-based notificationis going off, in accordance with embodiments described above.

Accordingly, output of an audio identifier when two or more time-basednotifications were previously set and at least one is still active whileone is going off provides the user with useful information regardingwhich of the time-based notifications is currently causing output of anaudio notification. For example, a user can start the TEN MINUTE timer afew minutes after the FIFTEEN MINUTE timer (as shown in FIGS. 8D-8E),but be unsure of which will expire first (e.g., the user does not haveknowledge of whether at least five minutes have elapsed from the FIFTEENMINUTE timer when the TEN MINUTE timer is set). Thus, announcing thename of a single time-based notification going off when there is atleast one other time-based notification active, even though only asingle-event condition exists, provides useful information about thestate of the device.

In some embodiments, the name output condition that is met when at leastone other time-based notification is active when a first time-basednotification's notification condition occurs additionally requires thatthe at least one other time-based notification is a notification of thesame type. For example, where the at least one other time-basednotification is a notification of a different type, an audio identifier(e.g., name) of the time-based notification that has expired will not beannounced. For example, if FIFTEEN MINUTE timer (TIMER 2) active in FIG.8F was instead an alarm type of notification, electronic device 600would not output the name of the TEN MINUTE timer upon expiration (e.g.,would instead output audio output 808 of FIG. 8C, which only includes anaudio notification). For example, the alarm type of notification couldbe an alarm that expires fifteen minutes from the time of its creation,such as an alarm created at 6:15 pm that expires at 6:30 pm. In thisexample, even if the FIFTEEN MINUTE timer would have expired at theexact same time (e.g., 6:30 pm) if the user had set a timer (e.g., TIMER2 of FIG. 8F) instead of an alarm, because the alarm is of a differenttype than the TEN MINUTE timer, an audio identifier (e.g., name) for thealarm would not be output because the condition that the time-basednotifications be the same type would not be met.

Accordingly, when there is only one of a first type (e.g., a timer) andone of a second type (e.g., an alarm) that were active before one ofthem expired, the device can indicate which expired by outputting atype-specific audio notification. For example, as described above, thefirst type of time-based notification can have a single-event audionotification for the first type, and the second type of time-basednotification can have a single-event audio notification for the secondtype. Thus, when a single event occurs, the particular single-eventaudio notification that is output provides an indication to the userabout which of the two types of time-based notifications have expiredand are currently causing audio notification output. In such case, anaudio identifier is not necessary.

In some embodiments, a name output condition is met when two or moretime-based notifications have expired and have not been dismissed. Forexample, turning briefly back to FIG. 6K, it illustrates the scenario inwhich two timers (TIMER 1 named “TEN MINUTE” and TIMER 2 named “FIVEMINUTE”) have both expired and have not been dismissed. As shown, audiooutput 622 includes an audio indicator for the time-based notificationthat has just expired (TEN MINUTE timer, as shown about to expire inFIG. 6G while FIVE MINUTE timer has already expired). Additionally,audio output 622 includes an audio indicator for the other time-basednotification that has expired (FIFTEEN MINUTE timer). Thus, audio output622 includes the text-to-speech dictation “TEN MINUTE AND FIFTEEN MINUTETIMERS” that identifies each of the timers that have expired.

In some embodiments, the name output condition that is met when two ormore time-based notifications have expired and have not been dismissedis met regardless (independent of) of the type(s) of the two or moretime-based notifications. For example, if an alarm and a timer haveexpired and not been dismissed, the electronic device will output thenames of both (e.g., together with a multiple-event audio notification).For example, if the two time-based notifications in FIG. 6K were atinier and an alarm, electronic device would still output audioidentifiers for both time-based notifications, such as “SIX THIRTY P.M.ALARM AN D TEN MINUTE TIMER”. Further, if an alarm type multiple-eventaudio notification takes priority over a timer type multiple-event audionotification (e.g., a multiple-event audio notification for the alarmtype of notification is output so long as the multiple-event conditionincludes at least one alarm going off), then the output of audioidentifiers serves to indicate that at least one timer has also expired,even though the multiple-event audio notification corresponding toalarms is being output. Thus, while a multiple-event audio notificationindicates that multiple time-based notification conditions haveoccurred, the output of audio indicators can provide an indication ofwhich time-based notifications have expired. Such information is useful,for example, where multiple time-based notifications have expired, butthere is still one or more other unexpired time-based notification.

FIGS. 8G-8N illustrate exemplary techniques for setting a name of atime-based notification.

FIGS. 8G-8H illustrate a technique for setting a name of a time-basednotification when creating the time-based notification. In someembodiments, the electronic device (e.g., 600) receives a request tocreate a time-based notification that includes a request to set a nameof the time-based notification. For example, in FIG. 8G, electronicdevice 600 receives voice input 816 that includes both a request tocreate a time-based notification (e.g., “HEY SIRI, SET A TIMER FOR TENMINUTES . . . ”) and a request to set a name for that time-basednotification (e.g., “ . . . CALLED DINNER”). In response to receivingvoice input 816, electronic device 600 sets a ten minute timer called“DINNER”. For example, as shown in status box 801 of FIG. 8G, beforevoice input 816, no timers are set, and after voice input 816, TIMER 1(called “DINNER”) has been set and has 9:59 (nine minutes and fifty-nineseconds) remaining. Additionally, in this example, electronic device 600provides acknowledgement 818 that the requested time-based notificationhas been created. In this example, acknowledgement 818 also includesconfirmation that the timer was successfully named “DINNER” by theoutput of: “TEN MINUTE DINNER TIMER, STARTING NOW”.

FIG. 8H illustrates expiration of a single time-based notification thatwas set based on a name received via user input. In some embodiments, aname output condition is met when a time-based notification has beennamed based on a received (e.g., via user input) request to set a nameof the time-based notification. For example, as shown in FIG. 8H, inresponse to expiration of the DINNER timer (status box 801 in FIG. 8Hshows it has no time remaining), the electronic device 600 outputs audiooutput 820. Audio output 820 includes an audio notification (e.g., asingle-event audio notification for a timer type notification) as wellas an audio identifier for the time-based notification (e.g., thetext-to-speech dictation output of the name “DINNER TIMER”). In thissituation, the name output condition is satisfied because device 600received an explicit request to set the name of the timer to aparticular name specified via user input (e.g., 816). Accordingly, inthis example, since a user specifically set a particular name for atimer, device 600 announces that name when the timer expires.

As described above with respect to timers, a name can be set for analarm in similar fashion. For example, a voice input of “HEY SIRI, SET AWAKE UP ALARM FOR SEVEN FIFTEEN A.M.” causes device 600 to set an alarmtype of time-based notification with the notification condition beingthe occurrence of the next 7:15 am time of day, and to set the name tobe “WAKE UP”. Upon occurrence of the 7:15 am notification condition,device 600 can output an audio identifier using the name WAKE UP (e.g.,when a name output condition is satisfied). For example, device 600causes output (e.g., in a predetermined pattern) of an alarm type audionotification and the statement “WAKE UP ALARM”.

In some embodiments, the electronic device (e.g., 600) sets a defaultname for a time-based notification if no request to set a name isreceived. For example, turning back to FIGS. 8A-8B, they illustrate thescenario in which the user does not specify a name for the ten minutetimer to be created (e.g., voice input 804 only includes a request tocreate the timer: “HEY SIRI, SET A TIMER FOR TEN MINUTES”). Accordingly,as shown in status box 801 in FIG. 8B, the name of the resulting timerthat is set (TIMER 1) is named “TEN MINUTE” (the name being specifiedwithin the parentheses). In some embodiments, the default name is a timevalue representing the time-based notification condition of thetime-based notification. In some embodiments, a time value is a lengthof time of the timer. For example, because no name is specified in FIG.8A, in FIG. 8B, TIMER 1 was given the name “TEN MINUTE” because itsoriginal length of time was ten minutes. In some embodiments, a timevalue is a time of day at which an alarm expires. For example, if analarm had been set in FIG. 8A instead of a timer (e.g., via the voiceinput “HEY SIRI, SET AN ALARM FOR SEVEN FIFTEEN A.M.”), a default namecould be the time value based on the notification condition of the timeof day “7:15 am”. Thus, upon output of a text-to-speech dictation of thedefault name, device 600 would output “SEVEN FIFTEEN A.M. ALARM,starting now” (e.g., in an acknowledgement) and “SEVEN FIFTEEN A.M.ALARM” (e.g., upon occurrence of the notification condition—the clockreaching 7:15 am).

FIGS. 8I-8J illustrate exemplary techniques for renaming a time-basednotification after is has been set, and an exemplary scenario in which arequested name is not available. In some embodiments, the electronicdevice (e.g., 600) receives a request to set a name of a time-basednotification after the time-based notification has already been set(e.g., in memory of device 600). For example, as shown in FIG. 8I,before device 600 receives voice input 822, TIMER 1 (named “TEN MINUTE”)is currently set and has not yet expired. Voice input 822 includes thestatement: “HEY SIRI, RENAME MY TEN MINUTE TIMER TO “DINNER””.Electronic device 600 parses voice input 822 to determine that the timernamed “TEN MINUTE” should be renamed to be called “DINNER”. Notably, atimer (TIMER 2) named DINNER already exists, as shown in status box 801in FIG. 8I.

Turning to FIG. 8J, a technique for outputting a prompt to provide a newname when a requested name is unavailable is illustrated. In someembodiments, in accordance with a determination that a requested name isunavailable, the electronic device outputs a prompt to provide analternate name (e.g., different than the requested name). For example,in FIG. 8J, in response to receiving voice input 822, electronic device600 outputs prompt 824 (e.g., a text-to-speech dictation) to provideanother name that includes the statement: “THERE'S ALREADY A TIMERCALLED DINNER, BUT I CAN SET ANOTHER. WHAT SHOULD I NAME THIS ONE?” Insome embodiments, a name is unavailable if another time-basednotification exists that already has that name. In this example, becauseTIMER 2 is already named DINNER, the name DINNER is not available forTIMER 1.

In some embodiments, a name is unavailable if it does not meet one ormore naming criterion. For example, the one or more naming criterion caninclude one or more of: a maximum length (e.g., number of characters), aminimum length, a requirement that the name does not containunacceptable words and/or characters, or the like. In some embodiments,a name is unavailable if it cannot be understood by the electronicdevice (e.g., transcribed by a speech-to-text algorithm).

In the example in FIG. 8J, after the electronic device 600 outputs audioprompt 824, the device detects voice input 826. Voice input 826 includesa new name, “CHICKEN”, different than the first name requested by theuser (DINNER). In some embodiments, in response to receiving a new name(e.g., via voice input) and in accordance a determination that the newname is available, the electronic device (e.g., 600) renames thetime-based notification with the new name. For example, in FIG. 8J,after receiving the new name CHICKEN in voice input 826, device 600renames the TEN MINUTE timer (TIMER 1 in FIG. 8I) to be named “CHICKEN”(as shown in status box 801 in FIG. 8J). In this example, the nameCHICKEN was available, so the electronic device sets the name of TIMER 1to CHICKEN. Optionally, electronic device 600 provides an exemplaryacknowledgement 828 including the statement: “OK, RENAMING YOUR TENMINUTE TIMER TO “CHICKEN””, confirming that the time-based notificationhas been renamed, and confirming the new name.

In some embodiments, in accordance with a determination that no new nameis received, the electronic device does not rename the time-basednotification. For example, if device 600 does not receive voice input826 (e.g., the user does not respond to prompt 824), the device does notrename the TEN MINUTE tinier. In some embodiments, the electronic devicewaits for a new name for a predetermined amount of time. For example,the device may wait and listen (e.g., using a microphone) for the newname for five seconds before ceasing to wait and ending the interaction(e.g., after which voice input of “CHICKEN” would have no effect ondevice 600 until the user makes another request such as 822).

In some embodiments, in accordance with a determination that a requestedname is available, the electronic device forgoes outputting a prompt toprovide an alternate name (e.g., 824) and renames the time-basednotification based on the request. For example, if TIMER 2 was not namedDINNER in FIG. 8I when voice input 822 is received, then electronicdevice would not output prompt 824, but would instead cause TIMER 1 tobe renamed to DINNER. In such case, the electronic device 600 couldoutput an audio acknowledgement such as “OK, RENAMING YOUR TEN MINUTETIMER TO “DINNER””.

FIGS. 8K-8N illustrate exemplary techniques for outputting a prompt toprovide a name when a time-based notification already exists that hasthe same default name as a new requested time-based notification. FIGS.8K-8L illustrate the creation of a first timer. In FIG. 8K, device 600receives voice input 830 requesting creation of a first time-basednotification, a timer for ten minutes. Voice input 830 includes thephrase: “HEY SIRI, SET A TIMER FOR TEN MINUTES”. Before voice input 830is received, no time-based notifications are active.

Turning to FIG. 8L, in response to receiving voice input 830, electronicdevice 600 sets a timer (TIMER 1) called “TEN MINUTE” having a length often minutes (e.g., shown to have elapsed one second with 9:59 (nineminutes and fifty-nine seconds) remaining in status box 801 of FIG. 8L.Additionally, electronic device 600 outputs acknowledgement 832: “TENMINUTE TIMER, STARTING NOW”. In this example, because electronic devicehas not received a request to set the name of the timer, it has assigneda default name to the timer, which is “TEN MINUTE” (based on the timevalue of the notification condition of the time-based notification).

FIGS. 8M-8N illustrate an exemplary technique for handling a request tocreate a second time-based notification that would have the same defaultname as an existing time-based notification. In FIG. 8M, TIMER 1 isactive (created as shown in FIGS. 8K-8L) and is named “TEN MINUTE”(e.g., a default name), as shown in status box 801. While TIMER 1 isactive, electronic device receives voice input 834, that includes arequest to set another ten minute timer and that does not include arequest to set the name of the new timer to a custom name. In someembodiments, in accordance with a determination that a request to createa time-based notification would result in a time-based notification thathas the same default name of an existing time-based notification, theelectronic device outputs a prompt (e.g., 836) to provide an alternativename. For example, in FIG. 8M, device 600 outputs prompt 836, whichincludes the statement: “THERE'S ALREADY A TEN MINUTE TIMER, BUT I CANSET ANOTHER. WHAT SHOULD I CALL THIS ONE?” In this example, afteroutputting prompt 836, electronic device 600 awaits input (e.g., voiceinput) of a new name (e.g., waits for a predetermined amount of time).As shown in FIG. 8M, after outputting prompt 836, electronic devicereceives voice input 838 that includes a new name “DINNER”.

Turning to FIG. 8N, in response to receiving the new name “DINNER” (FIG.8M), the electronic device sets a second ten minute timer (TIMER 2)named “DINNER”, in addition to the first, existing ten minute timernamed “TEN MINUTE”, as shown in status box 801. Additionally, electronicdevice 600 provides an exemplary acknowledgement 840 “TEN MINUTE DINNERTIMER, STARTING NOW”. As can be seen, exemplary acknowledgement 840includes an acknowledgement of the type (e.g., timer), the notificationcondition (e.g., ten minute), and the name (e.g., DINNER) for thetime-based notification that was just set.

FIG. 8O illustrates an exemplary technique for determining whether anaudio identifier (e.g., a name) of a time-based notification will beannounced (e.g., upon expiration of the time-based notification). Therows of table 842 in FIG. 8O respectively illustrate one of fourexemplary scenarios involving two time-based notifications (NOTIFICATION1 and NOTIFICATION 2), where one time-based notification (NOTIFICATION1) has expired and has not been dismissed and one time-basednotification (NOTIFICATION 2) is active (e.g., has not expired). Asdescribed above, an electronic device is capable of setting a first typeof time-based notification and a second type of time-based notification.For example, a first type can be a timer type of notification and asecond type can be an alarm type of notification. In another example,the first type is an alarm and the second type is a timer. As describedabove, in some embodiments, an exemplary name output condition is metwhen a first time-based notification expires when another time-basednotification is active and both are of the same type. Thus, toillustrate, in rows 842A and 842D, both NOTIFICATION 1 and NOTIFICATION2 are the same type (e.g., both a first type or both a second type), sothe name of NOTIFICATION 1 will be announced (e.g., similar to as shownin audio output 814 in FIG. 8F). Standing in contrast, in rows 842B and842C, NOTIFICATION 1 and NOTIFICATION 2 are not the same type (e.g., ineach scenario, one is a first type and the other is a second type), sothe name of NOTIFICATION 1 will not be announced (e.g., similar to asshown in audio output 808 in FIG. 8C).

FIGS. 9A-9B is a flow diagram illustrating a method for outputting audioidentifiers for time-based notifications using an electronic device inaccordance with some embodiments. Method 900 is performed at a device(e.g., 100, 300, 500, 580). Some operations in method 900 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 900 provides an intuitive way of outputtingaudio identifiers for time-based notifications. The method reduces thecognitive burden on a user for identifying expired time-basednotifications, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user toidentify expired time-based notifications faster and more efficientlyconserves power and increases the time between battery charges.

The electronic device (e.g., 600) receives (902) informationrepresenting a first time-based notification condition (e.g., a timerlength or an alarm time). For example, device 600 receives voice input804 in FIG. 8A, including the time-based notification condition of atimer of length ten minutes.

The electronic device (e.g., 600) sets (904) a first time-basednotification (e.g., TIM ER 1 in FIG. 8B) based on the first time-basednotification condition (e.g., timer of length ten minutes).

In response to a determination (906) that the first time-basednotification condition has occurred (e.g., timer expires, alarm timearrives) (e.g., TIMER 1 expires in FIG. 8C or 8F): the electronic device(e.g., 600) causes (908) output of an audio notification (e.g., asingle-event or multiple-event notification audio notification) (e.g.,audio output 808 of FIG. 8C, or audio output 814 of FIG. 8F), and inaccordance with a determination that a set of one or more name outputconditions is satisfied, the electronic device (e.g., 600) causes (910)output of an audio identifier (e.g., name) that identities the firsttime-based notification (e.g., audio output 814 of FIG. 8F, whichincludes the audio identifier “TEN MINUTE TIMER” identifying of theexpired exemplary first time-based notification TIMER 1). In someembodiments, the set of one or more name output conditions includes(912) a first condition that is satisfied when a second time-basednotification is active (e.g., the second time-based notification waspreviously set based on a (second) time-based notification condition,that condition has not yet occurred, and the second time-basednotification has not been canceled) when the first time-basednotification condition occurs. For example, if a second timer or secondalarm is set (e.g., for a future time) and is not expired at the timethat the first timer or first alarm goes off, the electronic deviceannounces the name of the first timer or first alarm going off). In someembodiments, the set of one or more name output conditions is satisfied(913) when at least one name output condition in the set of one or morename output conditions is satisfied. For example, if the set of one ormore name output conditions includes two or more (e.g., independent)conditions that can be satisfied (e.g., independently), thensatisfaction of fewer than (e.g., one) all can satisfy the set of one ormore name output conditions.

Outputting an audio identifier in accordance with a set of one or morename output conditions being satisfied provides the user with audiofeedback about the particular time-based notification that has expired.Providing improved audio feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In response to the determination (906) that the first time-basednotification condition has occurred, and in accordance with adetermination that the set of one or more name output conditions is notsatisfied, the electronic device (e.g., 600) forgoes (911) causingoutput of the audio identifier that identifies the first time-basednotification (e.g., audio output 808 of FIG. 8C, which does not includean audio identifier).

In some embodiments, a determination that the first condition issatisfied further includes a determination (914) that the firsttime-based notification and the second time-based notification are of asame type of time-based notification. For example, such a condition issatisfied when both time-based notifications are alarm type oftime-based notifications, or when are both time-based notifications aretimer type time-based notifications (e.g., but not when one is a timerand one is an alarm). As shown in FIG. 8F, exemplary first timer hasexpired, TIMER 1, is the same type (a timer type) of time-basednotification as exemplary second time-based notification TIMER 2(active), so an audio identifier (e.g., name) identifying TIMER 1 isoutput by device 600. FIG. 8O illustrates exemplary scenarios fordetermining when a condition requiring that notifications be of a sametype is satisfied. In some embodiments, the condition can work for onetype but not the other (e.g., satisfied by two timers, but not by twoalarms).

Outputting an audio identifier in accordance with a name outputcondition that includes a determination that a first (expired) andsecond (active) time-based notification are the same type of time-basednotification provides the user with audio feedback about the particulartime-based notification that has expired. Providing improved audiofeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first time-based notification and the secondtime-based notification are each either a first type of time-basednotification (e.g., a timer) or a second type of time-based notification(e.g., an alarm). In some embodiments, a notification condition for thefirst type of time-based notification occurs upon expiration of adetermined length of time (e.g., non-zero length of time; such as fiveminutes). In some embodiments, a notification condition for the secondtype of time-based notification occurs upon arrival of a determined timeof day (e.g., 5:32 pm).

In some embodiments, a third time-based notification (e.g., TIMER 2 ofFIG. 6K) was previously set (916) based on a third time-basednotification condition (e.g., five-minute length of time), and the setof one or more name output conditions includes a second condition thatis satisfied when the third time-based notification condition hasoccurred and the third time-based notification has not been dismissedwhen the first time-based notification condition occurs. For example, asshown in FIG. 6K, when at least two time-based notifications arecurrently expired and not dismissed, the audio identifier (e.g., “TENMINUTE”) identifying the first time-based notification (e.g., TIMER 1)is output by device 600. In some embodiments, the audio identifieridentifying the first time-based notification is output when at leasttwo time-based notifications (e.g., including the first time-basednotification) are currently expired and not dismissed, regardless of thetype of the at least two time-based notifications. For example, if analarm and a timer are both going off, the name for one (or both) can beoutput.

Outputting an audio identifier in accordance with a name outputcondition that is satisfied when two (e.g., or more) time-basednotifications have expired provides the user with audio feedback aboutthe particular time-based notification that has expired. Providingimproved audio feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the second condition is satisfied, and inaccordance with the determination (910) that the set of one or more nameoutput conditions is satisfied, the electronic device (e.g., 600)additionally causes output (918) of: the audio identifier thatidentifies the first time-based notification; and an audio identifierthat identifies the third time-based notification. For example, as shownin FIG. 6K, when at least two time-based notifications are currentlyexpired and not dismissed, an audio identifier (e.g., “TEN MINUTE”)identifying an exemplary first time-based notification (e.g., TIMER 1)and an audio identifier (e.g., “FIVE MINUTE”) identifying an exemplarythird time-based notification (e.g., TIMER 2) are output by device 600as audio output 622, which includes the statement: “TEN MINUTE AND FIVEMINUTE TIMERS”.

Outputting audio identifiers that identify each of two time-basednotifications corresponding to time-based notification conditions thathave occurred provides the user with audio feedback about the particulartime-based notifications that have expired. Providing improved audiofeedback to the user enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, a name of the first time-based notification isconfigurable via input (e.g., voice input) representing a request to setthe name of the first time-based notification (e.g., voice input 816 ofFIG. 8G). In some embodiments, the set of one or more name outputconditions includes (920) a third condition that is satisfied when thename of the first time-based notification has been configured via inputrepresenting a request to set the name of the first time-basednotification. For example, device 600 receives user input that providesa name for the timer or alarm at the time of creation (e.g., voice input816 of FIG. 8G), or after creation (e.g., renaming a time-basednotification) (e.g., voice input 822 of FIG. 8I, voice input 838 of FIG.8M).

Outputting an audio identifier in accordance with a name outputcondition that is satisfied when a request to set the name of a firsttime-based notification is received provides the user with audiofeedback about the particular time-based notification that has expired.Providing improved audio feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the electronic device (e.g., 600) receives inputrepresenting a request to set the name of the first time-basednotification to a first name (e.g., voice input 816 of FIG. 8G, voiceinput 822 of FIG. 8I, voice input 838 of FIG. 8M). In response toreceiving the input representing the request to set the name of thefirst time-based notification to the first name: in accordance with adetermination that the first name is available (e.g., is not being used,is permissible (e.g., not too long)), the electronic device (e.g., 600)sets the name of the first time-based notification to the first name(e.g., in FIG. 8O, TIMER 1 is named DINNER after receiving voice input816); and in accordance with a determination that the first name is notavailable (e.g., there is already a timer with that name, name is notpermissible), the electronic device (e.g., 600) forgoes setting the nameof the first time-based notification to the first name (e.g., in FIG.8J, device 600 forgoes naming TIMER 1 to DINNER). In some embodiments, adefault name is used instead (e.g., if an alternative name is notprovided).

In some embodiments, causing output of the audio identifier comprises,while the name of the first time-based notification is set to the firstname, causing audio output of the first name. For example, as shown inFIG. 8H, the audio identifier in audio output 820 is the output of thename of the time-based notification. In FIG. 8I, the name is the userspecified name “DINNER”.

In some embodiments, receiving the input representing the request to setthe name of the first time-based notification comprises receiving inputrepresenting a request to create the first time-based notification(e.g., voice input 816 in FIG. 8G includes a request to create and arequest to name), wherein the request to create the first time-basednotification includes: the information representing the first time-basednotification condition (e.g., a timer of length ten minutes); and therequest to set the name of the first time-based notification (e.g., “SETA TIMER”). In some embodiments, further in response to receiving therequest to create the first time-based notification: the electronicdevice (e.g., 600) sets the name of the first time-based notification tothe first name (e.g., in FIG. 8H, TIMER 1 has been named DINNER).

In some embodiments, receiving the input representing the request to setthe name of the first time-based notification comprises receiving theinput representing the request to set the name of the first time-basednotification subsequent to setting the first time-based notificationbased on the first time-based notification condition (e.g., receivingvoice input 822 of FIG. 8I, after TIMER 1 was already set). For example,electronic device 600 receives the input and renames an existing timerto the first name, and upon the notification condition occurring, usesthe new (first) name as the audio identifier, instead of the previousname (e.g., default name before renaming).

In some embodiments, further in accordance with a determination that thefirst name is not available (e.g., as shown in FIGS. 8I-8J, there'salready a timer called DINNER when voice input 822 is received): theelectronic device (e.g., 600) causes output of a prompt (e.g., an audioprompt) (e.g., audio output 824) to provide an alternative namedifferent from the first name (e.g., “THERE'S ALREADY A TIMER CALLEDDINNER, BUT I CAN SET ANOTHER. WHAT SHOULD I NAME THIS ONE?”); and theelectronic device (e.g., 600) awaits input of the alternative name.While awaiting input of the alternative name (e.g., for a thresholdamount of time after outputting the prompt), the electronic device(e.g., 600) receives input (e.g., voice input 826) representing a secondname (e.g., CHICKEN) different from the first name (e.g., DINNER). Inresponse to receiving the input (e.g., 838) representing the second name(e.g., CHICKEN): in accordance with a determination that the second nameis available, the electronic device (e.g., 600) sets the name of thefirst time-based notification to the second name (e.g., TIMER 1 is namedCHICKEN in FIG. 83 ); and in accordance with a determination that thesecond name is not available, forgoing setting the name of the firsttime-based notification to the second name. In some embodiments, ifinput representing the second name is not received (e.g., within athreshold amount of time after outputting the prompt), the electronicdevice does not set the time-based notification if the naming requestwas included in the request to create the time-based notification. Forexample, if voice input 838 is not provided in response to prompt output836, then device 600 would not create a second ten minute timer, TIMER 2(of FIG. 8N). In some embodiments, if the request was a request torename the time-based notification (e.g., received after the time-basednotification was already set), and the second name is not received, theelectronic device can forgo renaming the time-based notification (e.g.,and keep the previous name).

In some embodiments, in response to receiving the informationrepresenting the first time-based notification condition (e.g.,receiving voice input 834 of FIG. 8M), wherein the electronic device hasnot received a request to set a name of the first time-basednotification (e.g., in FIG. 8M, voice input 834 does not include arequest to set a same of the ten minute timer being created): inaccordance with a determination that a fourth time-based notification(e.g., TIMER 1 of FIG. 8M) is active, wherein the fourth time-basednotification was previously set based on a fourth time-basednotification condition (e.g., timer of length ten minutes), and whereinthe electronic device has not received a request to set a name of thefourth time-based notification condition (e.g., TIMER 1 in FIG. 8M hasdefault name TEN MINUTE), and wherein the first time-based notificationcondition (e.g., ten minutes as indicated by voice input 834) and thefourth time-based notification condition are the same (e.g., timerlength of ten minutes): the electronic device (e.g., 600) causes outputof a prompt (e.g., an audio prompt)(e.g., audio output 836) to provide acustom name for the first time-based notification; and awaits input ofthe custom name (e.g., voice input 838 includes exemplary custom name“DINNER”) for the first time-based notification. In response toreceiving the information representing the first time-based notificationcondition: in accordance with a determination that the fourth time-basednotification is not active (e.g., there is not currently a timer setwith the same default name): the electronic device (e.g., 600) sets thename of the first time-based notification to a first default name (e.g.,a timer length, an alarm time); the electronic device (e.g., 600)forgoes causing output of the prompt (e.g., 836) to provide the customname for the first time-based notification; and the electronic device(e.g., 600) forgoes awaiting input of the custom name for the firsttime-based notification. For example, as shown in FIGS. 8K-8L, when arequest to create a time-based notification does not include a requestto set a name, and another time-based notification does not alreadyexist that would have the same default name, the default name is used(e.g., TEN MINUTE for TIMER 1).

Outputting a prompt to provide a custom name for a time-basednotification when another time-based notification was previously setwith the same time-based notification condition provides the user withmore control of the device by helping the user unintentionally avoidcreating duplicate audio identifiers. Providing additional control ofthe device automatically without requiring repeated or excessive userinputs improved audio feedback to the user enhances the operability ofthe device and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the information representing the first time-basednotification condition does not include a request to set a name of thefirst time-based notification (e.g., voice input 804 does not include arequest to set a name), and the electronic device (e.g., 600) sets thename of the first time-based notification to a second default name(e.g., TEN MINUTE as shown in FIG. 8B), wherein the second default nameis based on a time value representing the first time-based notificationcondition; and wherein causing output of the audio identifier comprisescausing audio output of the second default name (e.g., audio output 814of FIG. 8F includes output of “TEN MINUTE TIMER”). In some embodiments,the time value is a length of time (e.g., 10 minutes). In someembodiments, the time value is a time of day (e.g., 5:00 pm).

Setting a default name for a time-based notification based on a timevalue when information representing the first time-based notificationcondition does not include a request to set a name of the firsttime-based notification reduces the number of user inputs required bythe user for determining a name to be used as an audio identifier.Performing an operation when a set of conditions has been met withoutrequiring further user input enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, causing output of the audio notification andcausing output of the audio identifier comprises causing output of theaudio notification and the audio identifier in a predetermined patternthat includes causing output of the audio notification a firstpredetermined number of times (e.g., two times) and causing output ofthe audio identifier that identifies the first time-based notification asecond predetermined number of times (e.g., one time). For example, asshown in FIG. 6K, audio output 622 includes a predetermined pattern inwhich an audio notification (AUDIO NOTIFICATION 2) is output twice,followed by output of an audio identifier (two in this example, “TENMINUTE AND FIVE MINUTE TIMERS”). In some embodiments, the electronicdevice causes output of the predetermined pattern to repeat (e.g., untildismissal of the notifications or expiration of a predetermined amountof time (e.g., 15 minutes). For example, in FIG. 6K, the pattern repeats(e.g., AUDIO NOTIFICATION 2 is shown being output another two timesafter the audio identifiers). In some embodiments, the firstpredetermined number of times increases to a third predetermined numberof times (e.g., four times) after the electronic device has causedoutput of the predetermined pattern a fourth predetermined number oftimes (e.g., after the pattern has repeated two times). For example, inFIG. 6L, the number of times that the audio notification AUDIONOTIFICATION 2 is output during one repetition of the predeterminedpattern has increased to four.

In some embodiments, the device outputs the audio notification the firstpredetermined number of times, followed by the audio identifier. In someembodiments, the device outputs the audio identifier followed by theaudio notification.

Note that details of the processes described above with respect tomethod 900 (e.g., FIGS. 9A-9B) are also applicable in an analogousmanner to the methods described above. For example, method 900optionally includes one or more of the characteristics of the variousmethods described above with reference to method 700. For example, thetechnique for determining the type of audio notification to output canbe combined with the technique for determining whether to output anaudio identifier. For brevity, these details are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of audio notifications. The present disclosurecontemplates that in some instances, this gathered data may includepersonal information data that uniquely identifies or can be used tocontact or locate a specific person. Such personal information data caninclude demographic data, location-based data, telephone numbers, emailaddresses, twitter IDs, home addresses, data or records relating to auser's health or level of fitness (e.g., vital signs measurements,medication information, exercise information), date of birth, or anyother identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver audio notifications that are more informative to the user.Further, other uses for personal information data that benefit the userare also contemplated by the present disclosure.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof time-based notification audio output, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In addition toproviding “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, audio outputfor time-based notifications can be selected and delivered to users byinferring preferences based on non-personal information data or a bareminimum amount of personal information, such as the content beingrequested by the device associated with a user, other non-personalinformation available to the time-based notification output service, orpublicly available information.

What is claimed is:
 1. An electronic device, comprising: one or moreprocessors; and memory storing one or more programs configured to beexecuted by the one or more processors, the one or more programsincluding instructions for: receiving a first information representing afirst time-based notification condition; setting a first time-basednotification based on the first time-based notification condition;detecting occurrence of the first time-based notification condition; andin response to detecting the occurrence of the first time-basednotification condition: in accordance with a determination that theelectronic device is not currently causing output of a notificationbased on at least one time-based notification other than the firsttime-based notification, causing output of a first visual indication;and in accordance with a determination that the electronic device iscurrently causing output of the notification based on at least onetime-based notification other than the first time-based notification,causing output of a second visual indication different from the firstvisual indication.
 2. The electronic device of claim 1, wherein: thefirst visual indication includes a first color; and the second visualindication includes a second color different from the first color anddoes not include the first color.
 3. The electronic device of claim 1,wherein: the first visual indication includes a first visual pattern;and the second visual indication includes a second visual patterndifferent from the first visual pattern.
 4. The electronic device ofclaim 3, wherein the first visual pattern and the second visual patternare animated.
 5. The electronic device of claim 1, wherein causingoutput of the first visual indication includes: in accordance with adetermination that a first number of time-based notifications areoccurring, causing output of the first visual indication with a firstappearance; and in accordance with a determination that a second numberof time-based notifications are occurring, causing output of the firstvisual indication with a second appearance different from the firstappearance.
 6. The electronic device of claim 1, further comprising atouch-sensitive surface and a display separate from the touch-sensitivesurface, wherein the first visual indication and the second visualindication are output via the display.
 7. The electronic device of claim1, the one or more programs further including instructions for: inresponse to detecting the occurrence of the first time-basednotification condition: in accordance with a determination that theelectronic device is not currently causing output of a notificationbased on at least one time-based notification other than the firsttime-based notification, causing output of a first audio notification;and in accordance with a determination that the electronic device iscurrently causing output of the notification based on at least onetime-based notification other than the first time-based notification,causing output of a second audio notification different from the firstaudio notification.
 8. The electronic device of claim 1, the one or moreprograms further including instructions for: while causing output of thefirst visual indication, detecting occurrence of a second time-basednotification condition; and in response to detecting the occurrence ofthe second time-based notification condition: ceasing output of thefirst visual indication; and causing output of the second visualindication different from the first visual indication.
 9. The electronicdevice of claim 1, wherein the first time-based notification conditionincludes one or more of: a first type of notification condition thatoccurs upon expiration of a determined length of time; and a second typeof notification condition that occurs upon arrival of a determined timeof day.
 10. A method comprising: at an electronic device: receiving afirst information representing a first time-based notificationcondition; setting a first time-based notification based on the firsttime-based notification condition; detecting occurrence of the firsttime-based notification condition; and in response to detecting theoccurrence of the first time-based notification condition: in accordancewith a determination that the electronic device is not currently causingoutput of a notification based on at least one time-based notificationother than the first time-based notification, causing output of a firstvisual indication; and in accordance with a determination that theelectronic device is currently causing output of the notification basedon at least one time-based notification other than the first time-basednotification, causing output of a second visual indication differentfrom the first visual indication.
 11. A non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device, the one or more programsincluding instructions for: receiving a first information representing afirst time-based notification condition; setting a first time-basednotification based on the first time-based notification condition;detecting occurrence of the first time-based notification condition; andin response to detecting the occurrence of the first time-basednotification condition: in accordance with a determination that theelectronic device is not currently causing output of a notificationbased on at least one time-based notification other than the firsttime-based notification, causing output of a first visual indication;and in accordance with a determination that the electronic device iscurrently causing output of the notification based on at least onetime-based notification other than the first time-based notification,causing output of a second visual indication different from the firstvisual indication.